[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Preparing for zfs filesystem
- To: silug-discuss@silug.org
- Subject: Re: Preparing for zfs filesystem
- From: "Robert G. (Doc) Savage" <dsavage@peaknet.net>
- Date: Sun, 09 Jun 2013 18:48:26 -0500
- In-Reply-To: <1369714473.3697.33.camel@lion.protogeek.org>
- Organization: Southern Illinois Linux Users Group
- References: <1982779818166890862@unknownmsgid> <1367115111.5162.40.camel@lion.protogeek.org> <1369714473.3697.33.camel@lion.protogeek.org>
- Reply-To: silug-discuss@silug.org
- Sender: silug-discuss-owner@silug.org
Trying to remove all traces of the old software RAID capability so
there's no conflict with the ZFS creation. So far I have:
1. Unmounted the array from its mountpoint:
# umount /pub
2. Removed the array's entry from /etc/fstab:
/dev/md127p1 /pub ext4 defaults 1 1
3. Disable creation of the array at next boottime:
# mv /etc/mdadm.conf /etc/mdadm.conf.backup
I've obviously missed something because upon reboot, dmesg says:
md: bind<sdj>
md: bind<sdf>
md: bind<sdi>
md: bind<sdk>
md: bind<sdg>
md: bind<sdh>
md: bind<sdd>
md: bind<sdc>
md: bind<sde>
async_tx: api initialized (async)
xor: automatically using best checksumming function: generic_sse
generic_sse: 10228.000 MB/sec
xor: using function: generic_sse (10228.000 MB/sec)
raid6: int64x1 2144 MB/s
raid6: int64x2 2992 MB/s
raid6: int64x4 2253 MB/s
raid6: int64x8 1992 MB/s
raid6: sse2x1 3160 MB/s
raid6: sse2x2 5472 MB/s
raid6: sse2x4 5878 MB/s
raid6: using algorithm sse2x4 (5878 MB/s)
raid6: using intx1 recovery algorithm
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
bio: create slab <bio-1> at 1
md/raid:md127: device sde operational as raid disk 2
md/raid:md127: device sdc operational as raid disk 0
md/raid:md127: device sdd operational as raid disk 1
md/raid:md127: device sdh operational as raid disk 5
md/raid:md127: device sdg operational as raid disk 4
md/raid:md127: device sdk operational as raid disk 8
md/raid:md127: device sdi operational as raid disk 6
md/raid:md127: device sdf operational as raid disk 3
md/raid:md127: device sdj operational as raid disk 7
md/raid:md127: allocated 9574kB
md/raid:md127: raid level 5 active with 9 out of 9 devices, algorithm 2
RAID conf printout:
--- level:5 rd:9 wd:9
disk 0, o:1, dev:sdc
disk 1, o:1, dev:sdd
disk 2, o:1, dev:sde
disk 3, o:1, dev:sdf
disk 4, o:1, dev:sdg
disk 5, o:1, dev:sdh
disk 6, o:1, dev:sdi
disk 7, o:1, dev:sdj
disk 8, o:1, dev:sdk
md127: detected capacity change from 0 to 2399712313344
md127: p1
Can someone please suggest what's doing the drive detection and logical
metadrive assembly?
--Doc
-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.