ccdconfig and Linux mdadm
Maciej Suszko
maciej at suszko.eu
Thu Jul 3 09:43:15 UTC 2014
Hi,
I'm wondering if anyone have tested or used ccd(4) to access md devices
created under Linux. According to ccdconfig(8) it should be possible
but I have no luck setting it up.
I created md0 under Linux (raid0, chunksize 512K):
root at lnx:~ # cat /proc/mdstat
Personalities : [raid1] [raid0]
md0 : active raid0 sdc1[1] sdb1[0]
523264 blocks super 1.2 512k chunks
root at lnx:~ # mdadm -D /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Thu Jul 3 11:06:21 2014
Raid Level : raid0
Array Size : 523264 (511.09 MiB 535.82 MB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Thu Jul 3 11:06:21 2014
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Chunk Size : 512K
Name : t2.vbox:0 (local to host t2.vbox)
UUID : b9927850:379de36b:82df9efc:6e7461af
Events : 0
Number Major Minor RaidDevice State
0 8 17 0 active sync /dev/sdb1
1 8 33 1 active sync /dev/sdc1
There is ext3 filesystem created directly on /dev/md0.
Now, trying to set up ccd device under FreeBSD-10-RELEASE amd64:
root at fbsd:~ # ccdconfig -c /dev/ccd0 512 linux /dev/ada1s1 /dev/ada2s1
root at fbsd:~ # ccdconfig -g
ccd0 1024 0 /dev/ada1s1 /dev/ada2s1
root at freebsd:~ # fsck.ext3 -n /dev/ccd0
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
fsck.ext3: Superblock invalid, trying backup blocks...
fsck.ext3: Bad magic number in super-block while trying to
open /dev/ccd0
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate
superblock: e2fsck -b 8193 <device>
Any ideas?
--
regards, Maciej Suszko.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20140703/e34bdbb5/attachment.sig>
More information about the freebsd-fs
mailing list