Hi Robin: I use mdadm cmd to create Raid5 device and did following: #mdadm --create /dev/md0 --level=5 --assume-clean --raid-devices=4 /dev/sda /dev/sdb /dev/sdc /dev/sdd #mdadm -w /dev/md0 mdadm: failed to set writable for /dev/md0: Device or resource busy ~ # mount none on /proc type proc (rw) none on /dev/shm type tmpfs (rw) none on /dev/pts type devpts (rw,mode=600) none on /sys type sysfs (rw) none on /mnth type hugetlbfs (rw) As u would notice, /dev/md0 is yet mounted...not sure why the above error.... Thanks for ur help! On Thu, Sep 17, 2009 at 1:02 PM, Robin Hill <robin@xxxxxxxxxxxxxxx> wrote: > On Thu Sep 17, 2009 at 12:23:22PM -0700, Linux Raid Study wrote: > >> Hello: >> >> I have to bundle 4 disks as a Raid5 device, export it to iSCSI >> initiators and format it as NTFS. >> >> What is better: >> - Format individual disks as NTFS and then bundle them as Raid5 device >> and export to initiator PCs >> - Or bundle the disks first as Raid5 dev, export them and then format >> the /dev/md0 device as NTFS >> >> I get "write-protected" errors when I do the second option. Does it >> mean formatting of raid5 device is not allowed? >> Does Raid5 inherit the NTFS properties of individual disks (first option)? >> > I don't see your first option working at all. When you bundle the > drives together, the resulting device will have totally scrambled the > underlying NTFS filesystems. > > The second option is how md RAID is supposed to work - you bundle > together the disks into a single array, then format that. Where are you > getting the "write-protected" errors? Are you trying to format the > exported iSCSI device from a remote system? Certainly the RAID device > can be formatted directly, but I've no idea how the iSCSI affects > things. > > HTH, > Robin > -- > ___ > ( ' } | Robin Hill <robin@xxxxxxxxxxxxxxx> | > / / ) | Little Jim says .... | > // !! | "He fallen in de water !!" | > -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
