Closed Smeeto13 closed 4 years ago
I have always used btrfs like this with success ... Why do you want to add a nested subvolume named @ in the /root subvolume ?
When I have used the script it has always installed to the btrfs root vol (level 5) instead of a sub vol
On Sat, 5 Sep 2020, 5:10 pm MatMoul, notifications@github.com wrote:
I have always used btrfs like this with success ... Why do you want to add a nested subvolume named @ in the /root subvolume ?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/MatMoul/archfi/pull/136#issuecomment-687630516, or unsubscribe https://github.com/notifications/unsubscribe-auth/APQ5EIN5WE3ENIIB3YWG6QDSEJPJFANCNFSM4Q23Z3EA .
Level 5 is a subvolume?
From what I have heard it is advised not to install to the top level vol because some features like drive expansion do not work if installed to the root vol
What do you mean with toplevel? Level 5 isn't ID 5.
this is the layout when setup with the changes I suggested and from my understanding the top one (level 5) does not work with all the features of btrfs
Looking on the doc : https://btrfs.wiki.kernel.org/index.php/SysadminGuide I don't find anything about limitation of subvolume, Level 5 or not. I use the standard flat layout explained in the page.
Adding a subvolume @ in root for the root of the system has nosense... Looking on OpenSuse, it has a @ subvolume at level5 and a root in it...
OK thank you for your time and looking into It
Fixes problems I had with installing to BTRFS root instead on sub vol