Summary: | Can't zero superblocks with sys-fs/mdadm-3.1.1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Juergen Rose
2010-03-07 12:33:43 UTC
root@sidux:~# mdadm --zero-superblock /dev/sda3 root@sidux:~# mdadm --zero-superblock /dev/sdb3 root@sidux:~# mdadm --create /dev/md4 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda3 /dev/sdb3 mdadm: /dev/sda3 appears to contain an ext2fs file system size=2008112K mtime=Sun Mar 7 11:35:36 2010 mdadm: /dev/sdb3 appears to contain an ext2fs file system size=2008112K mtime=Sun Mar 7 11:35:36 2010 Continue creating array? y mdadm: array /dev/md4 started. seems to work. Thanks for reporting this. Assigning to base-system for further investigation. i think the behavior you show is correct. dont superblocks exist on individual pieces and not the assembled device ? the error message you showed: mdadm: Unrecognised md component device - /dev/md4 and that's because /dev/md# is not a component device when you used the option on an actual component device, it seems to have worked fine |