On Friday, January 21, 2011 11:16:49 CACook@xxxxxxxxxxxxxxx wrote: > On Thu 20 January 2011 22:55:54 Hubert Kario wrote: > > You still have a btrfs on /dev/sdc, do a > > dd if=/dev/zero of=/dev/sdc bs=8192 > > (overkill, but I don't remember which blocks have to be zeroed to destroy > > btrfs superblock) > > I gave up and started over. Maybe it should be clarified in the wiki that > no mkfs should be done on additional volumes, as it's counterintuitive to > some. > > > yes. rc.local is too late, unless you will also mount the volume from > > there and not using /etc/fstab > > How and when then? in, or before /etc/rcS.d/S35mountall.sh > > > That depends - it has to be done before mounting. And if the device is > > part of the boot partition then you may put the "scan" command into an > > init-ramdisk. > > This does not seem to have been sent to the listserv, as I only got it in a > reply. This is likely incomplete. It was sent to list, your MUA may have merged messages with identical Message- ID. > > > Using something like "device=/dev/sdb,device=/dev/sdc" on fstab mount > > options should also work. > > You mean as a substitute for a scan? Would seem so, but I haven't tried this > > On my other server the btrfs array seems to mount just fine without any > measures to scan. I don't understand this, nor why no specific advice is > given about scanning on boot in the wiki. your distro may have alredy put it in initrd or initramfs (for example fedora and archlinux do) -- Hubert Kario QBS - Quality Business Software 02-656 Warszawa, ul. Ksawerów 30/85 tel. +48 (22) 646-61-51, 646-74-24 www.qbs.com.pl -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
