Re: [Solved (kind of)] Re: Installing Wheezy on btrfs only (multi-device)
On Sun, May 27, 2012 at 8:15 PM, Steven Post redalert.comman...@gmail.com wrote: On Sun, 2012-05-27 at 18:40 -0400, Tom H wrote: I was wondering about d-i's progress with btrfs so I tested Wheezy and Precise. Wheezy's current dailies and weeklies are broken so I'll wait for them to be fixed. For Precise, I chose just one partition (no /boot, no swap) and the installed (d-i not ubiquity, I didn't try the latter) and the installed created two subvolumes @ and @home for / and /home. This really sounds interesting, do you think support for multi-device btrfs and user controlled subvolumes will be fully supported by d-i by the time Wheezy is released? I doubt it because, AFAIK, the freeze is imminent. You'd said in a previous email that you didn't think that grub supported having /boot on a multi-device btrfs volume but in this grub-devel thread [1], the first email says that raid support hasn't been implemented and the last email says that it is. 1. http://web.archiveorange.com/archive/v/aVxzlidgDid2J9Mtd2eb That is very good news, that means it is just the d-i that can't handle it, a single device btrfs worked fine (at least in virtualbox), but d-i refused to install grub with my raid 10 btrfs volume. I created a 2-disk device using a live disk (mkfs.btrfs -L th -m raid1 -d raid1 /dev/sda1 /dev/sdb1) and Precise was installed on (I chose /dev/sda1 from the d-i partition menu) and was bootable, and sda was mirrored to sdb. I ran bootinfoscript after booting into the install and found that grub was installed in the MBR of sda but not of sdb. I ran grub-install /dev/sdb, re-ran bootinfoscript, and found that grub2's installed on sdb, but it's installed in the MBR of /dev/sdb and looks at sector 1 of the same hard drive for core.img. core.img is at this location and uses an embedded config file: (For the record, running grub-install /dev/sda installs grub on sda properly, without embedding.) I rebooted without sda connected and was dropped to an initramfs shell, so /boot-on-btrfs isn't yet ready for a multidevice setup; at least not without some extra work like, possibly, installing grub on sdb while booted from a live or rescue disk. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=sxpdy7r0zubv4cm+bvta_rcupccembdo4whvyvmggi...@mail.gmail.com
Re: [Solved (kind of)] Re: Installing Wheezy on btrfs only (multi-device)
On Mon, May 28, 2012 at 6:44 AM, Tom H tomh0...@gmail.com wrote: I created a 2-disk device using a live disk (mkfs.btrfs -L th -m raid1 -d raid1 /dev/sda1 /dev/sdb1) and Precise was installed on (I chose /dev/sda1 from the d-i partition menu) and was bootable, and sda was mirrored to sdb. I ran bootinfoscript after booting into the install and found that grub was installed in the MBR of sda but not of sdb. I ran grub-install /dev/sdb, re-ran bootinfoscript, and found that grub2's installed on sdb, but it's installed in the MBR of /dev/sdb and looks at sector 1 of the same hard drive for core.img. core.img is at this location and uses an embedded config file: (For the record, running grub-install /dev/sda installs grub on sda properly, without embedding.) I rebooted without sda connected and was dropped to an initramfs shell, so /boot-on-btrfs isn't yet ready for a multidevice setup; at least not without some extra work like, possibly, installing grub on sdb while booted from a live or rescue disk. 1. /boot on btrfs This is the changelog [a]. It's the first (last!) entry for 2011. a. http://packages.debian.org/changelogs/pool/main/p/partman-btrfs/partman-btrfs_8/changelog 2. Booting from initramfs shell I've tracked down the problem to the fact that $rootmnt is /root but, in the case of booting from one device of a degraded array, $rootmnt has to be /root/@. 3. grub-install on sda and sdb Even though the embedded config file isn't the reason for being dumped to an initramfs shell, I thought that I'd try to have grub installed the same way on both disks... Booted from a live disk, grub-probe fails when querying / inside and outside the chroot (for a an ext4 installs, it fails only outside the chroot so there's a problem with btrfs...). So I ran grub-install --boot-directory=/mnt/@/boot/grub /dev/sda and grub-install --boot-directory=/mnt/@/boot/grub /dev/sdb. I rebooted and ended up at a grub rescue prompt because the prefix was (hd0.msdos1)/boot/grub rather than (hd0,msdos1)/@/boot/grub. That pesky @ again... So I booted from a live disk, created a core.img with the correct prefix, installed it with grub-setup, and the VM's booting fine with both disks connected. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=Syg8yaXADwO+m2-7v=wv8kdd9ldvtnrohhgnnfh0cu...@mail.gmail.com
Re: [Solved (kind of)] Re: Installing Wheezy on btrfs only (multi-device)
On Sat, May 26, 2012 at 3:45 PM, Steven Post redalert.comman...@gmail.com wrote: On Mon, 2012-05-07 at 03:11 +0200, Steven Post wrote: It's been a while since I replied to this thread, and since I solved it (well.. kind of...) I thought I'd mention how I got this working in the end and also what happens when a drive fails. I don't have a blog, so I'll give it all here, it'll be a pretty long read. Perhaps only interesting to some. Many thanks for your follow-up. It's definitely of interest to me. I was wondering about d-i's progress with btrfs so I tested Wheezy and Precise. Wheezy's current dailies and weeklies are broken so I'll wait for them to be fixed. For Precise, I chose just one partition (no /boot, no swap) and the installed (d-i not ubiquity, I didn't try the latter) and the installed created two subvolumes @ and @home for / and /home. About a year ago, both Debian and Ubuntu needed a separate non-btrfs /boot and only one sub volume would be created on a partition, so there's progress; d-i can now create more than one subvolume on one partition but it's not yet user-controllable. Your method's still required for multi-device btrfs volumes. FYI, this is the grub.cfg linux line that's created: linux /@/boot/vmlinuz-... root=UUID=... ro rootflags=subvol=@ You'd said in a previous email that you didn't think that grub supported having /boot on a multi-device btrfs volume but in this grub-devel thread [1], the first email says that raid support hasn't been implemented and the last email says that it is. 1. http://web.archiveorange.com/archive/v/aVxzlidgDid2J9Mtd2eb -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=szssf8w3pdf4aq2lohwuqu83psw7x5r44gvajp4eeo...@mail.gmail.com
Re: [Solved (kind of)] Re: Installing Wheezy on btrfs only (multi-device)
On Sun, 2012-05-27 at 18:40 -0400, Tom H wrote: [...] Many thanks for your follow-up. It's definitely of interest to me. Glad someone found it useful. I was wondering about d-i's progress with btrfs so I tested Wheezy and Precise. Wheezy's current dailies and weeklies are broken so I'll wait for them to be fixed. For Precise, I chose just one partition (no /boot, no swap) and the installed (d-i not ubiquity, I didn't try the latter) and the installed created two subvolumes @ and @home for / and /home. About a year ago, both Debian and Ubuntu needed a separate non-btrfs /boot and only one sub volume would be created on a partition, so there's progress; d-i can now create more than one subvolume on one partition but it's not yet user-controllable. Your method's still required for multi-device btrfs volumes. This really sounds interesting, do you think support for multi-device btrfs and user controlled subvolumes will be fully supported by d-i by the time Wheezy is released? I think this would really benefit setups like mine. I'm also thinking home server setups, or production setups later on, once it isn't an experimental filesystem anymore. [...] You'd said in a previous email that you didn't think that grub supported having /boot on a multi-device btrfs volume but in this grub-devel thread [1], the first email says that raid support hasn't been implemented and the last email says that it is. 1. http://web.archiveorange.com/archive/v/aVxzlidgDid2J9Mtd2eb That is very good news, that means it is just the d-i that can't handle it, a single device btrfs worked fine (at least in virtualbox), but d-i refused to install grub with my raid 10 btrfs volume. I don't follow d-i development really, I just took a daily image to install the system. The only real drawback on my system once installed is the inability to use snapshots for /boot. Especially as Debian security updates for the kernel overwrite the existing one (haven't had a problem with that approach yet, but you never know). Regards, Steven signature.asc Description: This is a digitally signed message part
[Solved (kind of)] Re: Installing Wheezy on btrfs only (multi-device)
On Mon, 2012-05-07 at 03:11 +0200, Steven Post wrote:
It's been a while since I replied to this thread, and since I solved it
(well.. kind of...) I thought I'd mention how I got this working in the
end and also what happens when a drive fails.
I don't have a blog, so I'll give it all here, it'll be a pretty long
read. Perhaps only interesting to some.
Another attempt, mixed success.
I created the btrfs filesystem using the ubuntu live cd (2 subvolumes, 1
for the root fs, 1 for /home, and set rootfs as the default subvolume),
then started the Debian installation again from the daily netinstall
iso.
[...]
The installer only fails to install the grub bootloader, I think because
it cannot detect the multi-device btrfs file system.
I then opted for skipping installing a bootloader, figuring I could do
it afterwards in rescue mode. Installer finishes up without any further
problems.
As far as I know GRUB supports only single device btrfs file systems,
not multi-device. Having a single device btrfs for /boot would defeat
the idea of raid for /boot so I opted for something else.
All 6 drives have a 3 partitions, a very small one for BIOS boot, a
larger one (1GB) so /boot will fit (with a lot of space left), and the
rest is a single partition of about 2.7 TB. The last 2 partitions are
Linux partitions, the default gdisk suggests.
Next I use an Ununtu 12.04 install disk to setup my raid 10 btrfs volume
using the third (large) partition from each drive.
I create a couple of subvolumes for different purposes (one for the root
file system (/), one for /home etc..
Next I mark the subvolume for the root fs as the default subvolume (when
working with subvolumes this is needed because of the limitations in the
Debian installer).
Once btrfs is set up I restart the machine with the Wheezy netinstaller.
I choose a standard install and proceeded through the installer until I
got to the partitioner. When I'm in the partitioner, I use ctrl+alt+F2
to switch to a console. After pressing enter I'm greeted with a root
prompt, from here I issued a btrfs device scan using btrfsctl -a as
the installer doesn't have the btrfs command. I can then switch back to
the partitioner using ctrl+alt+F1 and mark the 3rd partition from one of
the 6 drives as my root filesystem (/) using btrfs as the filesystem,
making sure to have the option keep existing data enabled.
Still in the partitioner I choose to setup raid, I choose a md raid1
setup using 3 devices and 3 spares, these are the second partitions from
each drive. This array I mark for use with ext4, although I think btrfs
on top of this raid array would work, although I haven't tried it. I
proceed to mark this ext4 partition as /boot.
With both / and /boot I can continue with the install, notice I don't
have a swap partition, but in this case I felt I didn't need one,
everyone is free to add that if they want to or I can add it later
should the need arises. Anyway, I just continue the install as with any
system and once it is completed, I tell the installer to install grub on
every device, should a device fail, I can still boot the system.
After installation is complete I still need the installer (rescue mode)
or some live cd to fix /etc/fstab so it doesn't hang trying to do an
fsck on the btrfs root fs. When all this is done I can finally boot the
new system.
Now when a drive fails, as happened earlier today (I don't know why, but
I'll get a replacement this Tuesday), the system will fail to boot
properly after removing that drive, you are dropped in a busybox shell
and options are limited. Don't be alarmed, this is because the root
filesystem refuses to mount with a missing drive. In the mean time my
raid1 for /boot has taken a space device and is syncing it with the
other 2. I let it sync before continuing. When the syncing is done, I
reboot and when I get to the GRUB boot prompt I press 'e' to edit.
I look for the line starting with 'linux /vmlinuz' and add a rootflag
giving me something like this:
linux /vmlinuz-3.2.0-2-AMD64 root=UUID={some long uuid}
rootflags=degraded ro quiet
Adding this 'degraded' rootflag allows you're kernel to mount the root
filesystem again. Once started you can remove the missing drive from the
btrfs array and issue a btrfs filesystem balance / (provided you still
have enough space to mirror everything with that missing drive and at
least 4 drives), leaving you with a raid 10 system with 5 drives.
Later on I can shutdown the system (it's not hot swappable in my case),
add the new hard drive, partition it like before, add one partition to
the /boot raid array as a spare device, and add the large partition to
the btrfs array, balance again and I'm good to go.
If you have a replacement lying around, or not enough free space for the
balance with a drive out, you can omit that step and just add it right
away. But always balance after adding the device.
Should anyone have any comments or improvements, please them know. I'm
not such an
Re: Installing Wheezy on btrfs only (multi-device)
Hi, On Mon, May 07, 2012 at 03:11:36AM +0200, Steven Post wrote: ... I think with skill and knowledge you presented, if you are successful doing this with help of shell etc., you should present specific procedure needed to do this to d-i BTS as wishlist bug. That should get it supported smoothly for upcoming release. Good idea. If you have specific issues with grun, grub maintainer/BTS may be another option. Anyway, with your skill, you my get better reply from debian-b...@lists.debian.org . Good luck. Osamu -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120507135137.GA5328@localhost
Re: Installing Wheezy on btrfs only (multi-device)
On Sun, 2012-05-06 at 13:51 +0900, Osamu Aoki wrote: Hi, On Sat, May 05, 2012 at 01:24:59AM +0200, Steven Post wrote: Hello list, I'm testing out a new system, the idea is to combine 6 hard drives into a single btrfs volume (raid10) (using subvolumes for /, /home, etc). I understand that it is now possible to also have /boot on btrfs (previously impossible because of GRUB). I tried to install sysyem with much simpler configuration: / : a single btrfs on a partition /dev/sda1 swap: a single swap on a separate partition /dev/sda2 It did not work due to missing fsck.btrfs in btrfs-tools. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668832 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567681 I've had the same problem, but I was aware of it from an earlier attempt using virtualbox and a separate ext4 /boot partition. This can be solved by changing /etc/fstab (booting from a live cd), look for the line with the btrfs system, then change last number on that line to a '0' (the 'pass' column). Unfortunately the Debian installer (daily build for wheezy) is unable to create multi-device btrfs volumes. Yah.. but you probably can do this via shell screen. I don't think I'm able to do that from the rescue mode shell without using an existing installation, without the existing installation I get a 'Command not found' error on 'btrfs device scan', I assume this includes the whole btrfs command. I tried the a normal install and then copy it over to a multi-device btrfs system, afterwards adding the remaining disk: 1) using a single drive to install using ext4 for /boot and btrfs for / 2) after (successful) installation boot from a live cd (ubuntu 12.04 in this case, but it shouldn't really matter) How successful? Did it boot? It boots, yes, but you still need to change /etc/fstab using a live cd because of the missing fsck tool. 3) create partitions for btrfs on the other 5 drives using gdisk 4) create a multi-device btrfs filesystem with those partitions, with a subvolume for the root filesystem and for /home 5) copy all the data from the first disk to the new btrfs volume 6) chroot into the rootfs of the new volume, after mounting (-o bind) /dev, /proc and /sys into the mounted system 7) change fstab for the new drives and modify /etc/default/grub 8) run update-grub: this is where things start falling down, I get an error about / not being mounted so grub fails. This is apparently caused by a regression in GRUB [1] (Debian bug #538118). Well this is possibly another problem you are facing. Basically, you should know what file to change imanually when copying files from one partition to another. So this is really an expert trick which d-i currently does not support for ordinry uses. But as I mention in the above, most simple installation suffer major breakage for btrfs on wheezy even if you manually adjust configuration files. I'll have another look if my other attempts from within the d-i fails. Another thing I noticed during my tests is that the installer will recognize existing btrfs partitions and is able to use them, except when dealing with a multi-device file system. Using rescue mode you can trick d-i into using them properly by executing a shel in an existing installation, then issuing a btrfs device scan. Once the scan is done, you can exit the shell and go back to the partitioner. There I could select a device (partition) from the btrfs system and use it as /, now the mount works with the multi-device partition. Perhaps d-i should issue the 'btrfs device scan' command when starting the partitioner? Kind regards, Steven signature.asc Description: This is a digitally signed message part
Re: Installing Wheezy on btrfs only (multi-device)
Hi, On Sun, May 06, 2012 at 02:11:58PM +0200, Steven Post wrote: On Sun, 2012-05-06 at 13:51 +0900, Osamu Aoki wrote: Hi, On Sat, May 05, 2012 at 01:24:59AM +0200, Steven Post wrote: Hello list, I'm testing out a new system, the idea is to combine 6 hard drives into a single btrfs volume (raid10) (using subvolumes for /, /home, etc). I understand that it is now possible to also have /boot on btrfs (previously impossible because of GRUB). I tried to install sysyem with much simpler configuration: / : a single btrfs on a partition /dev/sda1 swap: a single swap on a separate partition /dev/sda2 It did not work due to missing fsck.btrfs in btrfs-tools. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668832 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567681 I've had the same problem, but I was aware of it from an earlier attempt using virtualbox and a separate ext4 /boot partition. This can be solved by changing /etc/fstab (booting from a live cd), look for the line with the btrfs system, then change last number on that line to a '0' (the 'pass' column). Yah, that's one way. My bug report cited another work around. Unfortunately the Debian installer (daily build for wheezy) is unable to create multi-device btrfs volumes. Yah.. but you probably can do this via shell screen. I don't think I'm able to do that from the rescue mode shell without using an existing installation, without the existing installation I get a 'Command not found' error on 'btrfs device scan', I assume this includes the whole btrfs command. It is easiest to do it using an existing installation. Well... I see btrfs-tools-udeb package. If you install via expermode, you may be able to chose to install btrfs-tools-udeb via menu. Otherwise, install such packages via wget and dpkg to rescue system provided you have enough memory I tried the a normal install and then copy it over to a multi-device btrfs system, afterwards adding the remaining disk: 1) using a single drive to install using ext4 for /boot and btrfs for / 2) after (successful) installation boot from a live cd (ubuntu 12.04 in this case, but it shouldn't really matter) How successful? Did it boot? It boots, yes, but you still need to change /etc/fstab using a live cd because of the missing fsck tool. Yes that is a start. I usually do this while installing with d-i CD in advance (or in rescure mode later which is essentially a live cd) 3) create partitions for btrfs on the other 5 drives using gdisk 4) create a multi-device btrfs filesystem with those partitions, with a subvolume for the root filesystem and for /home 5) copy all the data from the first disk to the new btrfs volume 6) chroot into the rootfs of the new volume, after mounting (-o bind) /dev, /proc and /sys into the mounted system 7) change fstab for the new drives and modify /etc/default/grub 8) run update-grub: this is where things start falling down, I get an error about / not being mounted so grub fails. This is apparently caused by a regression in GRUB [1] (Debian bug #538118). Well this is possibly another problem you are facing. Basically, you should know what file to change imanually when copying files from one partition to another. So this is really an expert trick which d-i currently does not support for ordinry uses. But as I mention in the above, most simple installation suffer major breakage for btrfs on wheezy even if you manually adjust configuration files. I'll have another look if my other attempts from within the d-i fails. Another thing I noticed during my tests is that the installer will recognize existing btrfs partitions and is able to use them, except when dealing with a multi-device file system. Using rescue mode you can trick d-i into using them properly by executing a shel in an existing installation, then issuing a btrfs device scan. Once the scan is done, This is my wild guess. btrfs support of d-i is not so mature yet. you can exit the shell and go back to the partitioner. There I could select a device (partition) from the btrfs system and use it as /, now the mount works with the multi-device partition. Perhaps d-i should issue the 'btrfs device scan' command when starting the partitioner? I think with skill and knowledge you presented, if you are successful doing this with help of shell etc., you should present specific procedure needed to do this to d-i BTS as wishlist bug. That should get it supported smoothly for upcoming release. Kind regards, Steven Osamu -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120506133012.GA15043@localhost
Re: Installing Wheezy on btrfs only (multi-device)
On Fri, 2012-05-04 at 20:33 -0400, Tom H wrote: [...] [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538118 I don't think that this bug corresponds to your problem because you're bind-mounting /dev. Does grub-probe work inside the chroot? grub-probe --target=abstraction / grub-probe --target=drive / grub-probe --target=fs / grub-probe --target=fs_uuid / grub-probe --target=partmap / I'm guessing it doesn't, unfortunately I can't verify anymore due to some other experimentation. Kind regards, Steven signature.asc Description: This is a digitally signed message part
Re: Installing Wheezy on btrfs only (multi-device)
On Sun, 2012-05-06 at 22:30 +0900, Osamu Aoki wrote: [...] Unfortunately the Debian installer (daily build for wheezy) is unable to create multi-device btrfs volumes. Yah.. but you probably can do this via shell screen. I don't think I'm able to do that from the rescue mode shell without using an existing installation, without the existing installation I get a 'Command not found' error on 'btrfs device scan', I assume this includes the whole btrfs command. It is easiest to do it using an existing installation. Another attempt, mixed success. I created the btrfs filesystem using the ubuntu live cd (2 subvolumes, 1 for the root fs, 1 for /home, and set rootfs as the default subvolume), then started the Debian installation again from the daily netinstall iso. Although the btrfs command isn't available from a shell, the btrfsctl command is, so I was able to issue a btrfsctl -a command, equivalent to btrfs device scan. Then in the partitioner I can select a single partition that is part of the btrfs file system and mark it to be used as the root fs /. The Debian-installer will then correctly mount the btrfs file system (all 6 drives) and use it to install. The installer only fails to install the grub bootloader, I think because it cannot detect the multi-device btrfs file system. I then opted for skipping installing a bootloader, figuring I could do it afterwards in rescue mode. Installer finishes up without any further problems. Installing grub from rescue mode (after manually issuing a btrfsctl -a command again) using the array as root fails with 'grub-install /dev/sda' telling me Auto-detection of a filesystem of /dev/sda2 failed. Every disk has 2 partitions, a 20 MB BIOS boot partition (I thought this might be needed because of the use of GPT partitions, not sure), the rest is allocated to a partition used for the btrfs filesystem. Currently I'm stuck there. I'll have a look at it again tomorrow. Well... I see btrfs-tools-udeb package. If you install via expermode, you may be able to chose to install btrfs-tools-udeb via menu. Otherwise, install such packages via wget and dpkg to rescue system provided you have enough memory btrfs-tools-udeb isn't available from the expert install, it is loaded anyway as part of the partitioner. [...] I think with skill and knowledge you presented, if you are successful doing this with help of shell etc., you should present specific procedure needed to do this to d-i BTS as wishlist bug. That should get it supported smoothly for upcoming release. Good idea. Kind regards, Steven Osamu signature.asc Description: This is a digitally signed message part
Re: Installing Wheezy on btrfs only (multi-device)
Hi, On Sat, May 05, 2012 at 01:24:59AM +0200, Steven Post wrote: Hello list, I'm testing out a new system, the idea is to combine 6 hard drives into a single btrfs volume (raid10) (using subvolumes for /, /home, etc). I understand that it is now possible to also have /boot on btrfs (previously impossible because of GRUB). I tried to install sysyem with much simpler configuration: / : a single btrfs on a partition /dev/sda1 swap: a single swap on a separate partition /dev/sda2 It did not work due to missing fsck.btrfs in btrfs-tools. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668832 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567681 Unfortunately the Debian installer (daily build for wheezy) is unable to create multi-device btrfs volumes. Yah.. but you probably can do this via shell screen. I tried the a normal install and then copy it over to a multi-device btrfs system, afterwards adding the remaining disk: 1) using a single drive to install using ext4 for /boot and btrfs for / 2) after (successful) installation boot from a live cd (ubuntu 12.04 in this case, but it shouldn't really matter) How successful? Did it boot? 3) create partitions for btrfs on the other 5 drives using gdisk 4) create a multi-device btrfs filesystem with those partitions, with a subvolume for the root filesystem and for /home 5) copy all the data from the first disk to the new btrfs volume 6) chroot into the rootfs of the new volume, after mounting (-o bind) /dev, /proc and /sys into the mounted system 7) change fstab for the new drives and modify /etc/default/grub 8) run update-grub: this is where things start falling down, I get an error about / not being mounted so grub fails. This is apparently caused by a regression in GRUB [1] (Debian bug #538118). Well this is possibly another problem you are facing. Basically, you should know what file to change imanually when copying files from one partition to another. So this is really an expert trick which d-i currently does not support for ordinry uses. But as I mention in the above, most simple installation suffer major breakage for btrfs on wheezy even if you manually adjust configuration files. Has anyone attempted such an install before? How should I proceed with this? Good luck. Kind regards, Steven [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538118 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120506045149.GA6661@localhost
Installing Wheezy on btrfs only (multi-device)
Hello list, I'm testing out a new system, the idea is to combine 6 hard drives into a single btrfs volume (raid10) (using subvolumes for /, /home, etc). I understand that it is now possible to also have /boot on btrfs (previously impossible because of GRUB). Unfortunately the Debian installer (daily build for wheezy) is unable to create multi-device btrfs volumes. I tried the a normal install and then copy it over to a multi-device btrfs system, afterwards adding the remaining disk: 1) using a single drive to install using ext4 for /boot and btrfs for / 2) after (successful) installation boot from a live cd (ubuntu 12.04 in this case, but it shouldn't really matter) 3) create partitions for btrfs on the other 5 drives using gdisk 4) create a multi-device btrfs filesystem with those partitions, with a subvolume for the root filesystem and for /home 5) copy all the data from the first disk to the new btrfs volume 6) chroot into the rootfs of the new volume, after mounting (-o bind) /dev, /proc and /sys into the mounted system 7) change fstab for the new drives and modify /etc/default/grub 8) run update-grub: this is where things start falling down, I get an error about / not being mounted so grub fails. This is apparently caused by a regression in GRUB [1] (Debian bug #538118). Has anyone attempted such an install before? How should I proceed with this? Kind regards, Steven [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538118 signature.asc Description: This is a digitally signed message part
Re: Installing Wheezy on btrfs only (multi-device)
On Fri, May 4, 2012 at 7:24 PM, Steven Post redalert.comman...@gmail.com wrote: I'm testing out a new system, the idea is to combine 6 hard drives into a single btrfs volume (raid10) (using subvolumes for /, /home, etc). I understand that it is now possible to also have /boot on btrfs (previously impossible because of GRUB). Unfortunately the Debian installer (daily build for wheezy) is unable to create multi-device btrfs volumes. I tried the a normal install and then copy it over to a multi-device btrfs system, afterwards adding the remaining disk: 1) using a single drive to install using ext4 for /boot and btrfs for / 2) after (successful) installation boot from a live cd (ubuntu 12.04 in this case, but it shouldn't really matter) 3) create partitions for btrfs on the other 5 drives using gdisk 4) create a multi-device btrfs filesystem with those partitions, with a subvolume for the root filesystem and for /home 5) copy all the data from the first disk to the new btrfs volume 6) chroot into the rootfs of the new volume, after mounting (-o bind) /dev, /proc and /sys into the mounted system 7) change fstab for the new drives and modify /etc/default/grub 8) run update-grub: this is where things start falling down, I get an error about / not being mounted so grub fails. This is apparently caused by a regression in GRUB [1] (Debian bug #538118). Has anyone attempted such an install before? How should I proceed with this? [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538118 I don't think that this bug corresponds to your problem because you're bind-mounting /dev. Does grub-probe work inside the chroot? grub-probe --target=abstraction / grub-probe --target=drive / grub-probe --target=fs / grub-probe --target=fs_uuid / grub-probe --target=partmap / -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=sykq9whl_ior1q+psq4+icawyoq-xvxf1jue9gcbe3...@mail.gmail.com
