On Tue, Oct 25, 2011 at 3:54 PM, dima <dole...@parallels.com> wrote: >>> Hi Fajar, >>> I think I am doing just this, but my subvolumes are not visible under >>> /boot. I >>> have all my subvolumes set up like this: >>> /path/to/subvolid_0/boot< a simple directory bind-mounted to / >>> /path/to/subvolid_0/__active< my / subvolume >>> /path/to/subvolid_0/__home< my /home subvolume >> >> Actually with that setup you're using option (3) that I described. >> >> That means all your subvolumes is still visible under >> /path/to/subvolid_0/, right? I'm not sure how well grub can manage >> this. Probably it can't, so you'd have to manage boot entries >> manually. > > Yes, you are right. I can see all subvolumes under /path/to/subvolid_0 > By the way grub2 can manage this setup correctly and generate the right menu > entries without any problems. > > But - /boot is not in its own subvolume in this setup. I think this is the > reason it works out of the box. > > Thank you for your explanations. > I can see if I can make it work with /boot in its own subvolume.
If you currently have it working, then as long as you have the full subvolid=0 mounted somewhere and use bind-mount from that, it shouldn't matter whether it's a subdir or a subvol. But if you mount the subvol directly in /boot, you'll have the same problem I do. So it's a trade off, I guess. You can have grub manage grub.cfg correctly, but you need to have the full tree mounted somewhere. Not ideal, but a possible option which I hadn't thought of before. Thanks for sharing your setup. -- Fajar -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
