On Tue, Apr 7, 2015 at 3:58 PM, Russell Coker <russ...@coker.com.au> wrote: > On Tue, 7 Apr 2015 10:58:28 AM arnaud gaboury wrote: >> After more reading, it seems to me creating a top root subvolume is >> the right thing to do: >> # btrfs subvolume create root >> # btrfs subvolume create root/var >> # btrfs subvolume create root/home >> >> Am I right? > > A filesystem is designed to support arbitrary names for files, directories, > and > in the case of BTRFS subvolumes. > > You might ask whether /var/log is a good place for log files, it's generally > regarded that "yes" is the correct answer to that question, but it's not a > question for filesystem developers. > > I like to have / in the root subvolume so all subvolumes are available by > default. I have /var etc in the same subvolume so I can make an atomic > snapshot of all such data. It's not the one true answer, but it works for me > and will work for other people. > > The main thing is to have all data that needs to be atomically snapshotted on > the same subvolume.
Would you mind give the return of # btrfs subvolume list and $ cat /etc/fstab ? It would help me. TY > > -- > My Main Blog http://etbe.coker.com.au/ > My Documents Blog http://doc.coker.com.au/ -- google.com/+arnaudgabourygabx -- 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
