On Mon, 11 Mar 2002, Neil Brown wrote: > On Saturday March 9, derek@cynicism.com wrote: > > > > mdadm: No super block found on /dev/md/3 (Expected magic a92b4efc, got > > > > 77315132). > > > > mdadm: No super block found on /dev/md/3 (Expected magic a92b4efc, got > > 77315132). Maybe you meant --detail? > > Yes, it seems that this is a very real problem. I'm not sure what the > best solution is though. > > One idea I have had is to have a --query mode (of which --detail and > --examine are considered submodes). > mdadm --query /dev/md1 It occurs to me that simply adding another mode (command line option) isn't going to fix this because it doesn't really make the differences between --detail and --examine clearer. All it does is add another layer to the same issue. > would tell you briefly about the array that md1 is, and about any > array that md1 is part of, and would suggest --detail or --examine to > get more information. Then the various documentation could highlight > --query in the hope that people would use it first. Hmmm.. so you mean that mdadm -Q /dev/md1 might print out something like: /dev/md1: 18GB RAID-1 (member disks: /dev/sda1, /dev/sdb1 spares: /dev/sdc1) Use -QD for more detail or -QE to examine member disks. --- Derek Vadala, derek@cynicism.com, http://www.cynicism.com/~derek - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
