On Feb 5, 2014, at 4:24 AM, Jorge Fábregas wrote:
> On 02/03/2014 03:16 PM, Chris Murphy wrote:
>> It seems to me that there will be some error message in the log
>> as the (stale) fstab tries to do a rw mount of a different subvol on
>> top of the one specified by rootflags=. Or maybe it succe
On Feb 5, 2014, at 4:23 AM, Jorge Fábregas wrote:
>
> I haven't follow the openSUSE community for years. Do you think they've
> nailed most of these issues? or all distros on the same boat ?
I'd say it's all pretty much up in the air. openSUSE uses snapper by default,
so they take snapshots r
On 02/03/2014 03:16 PM, Chris Murphy wrote:
> It seems to me that there will be some error message in the log
> as the (stale) fstab tries to do a rw mount of a different subvol on
> top of the one specified by rootflags=. Or maybe it succeeds silently,
> I haven't recently tested this scenario.
On 02/03/2014 03:16 PM, Chris Murphy wrote:
> Yes, there are challenges, much of which are the result of unanswered
> questions. For example:
>
> What should the layout be? (See opensuse's layout for an alternative to
> Fedora's.) How discoverable should this be for mortal users vs experts?
> How
On Feb 4, 2014, at 12:23 AM, James Hogarth wrote:
> The other fun thing I encountered the other day is that cp --reflink=always
> still doesn't work across mount points even if they are part of the same
> btrfs pool and therefore capable of using COW between subvolumes.
>
There are patches up
On 3 Feb 2014 18:26, "Chris Murphy" wrote:
> Note also that opensuse has a different layout for all of this than
Fedora. They make the default subvolume ID 5 (the top level of the Btrfs
file system, the first subvolume, the one that can't be deleted or named)
the parent and mount it at /. And then
On Feb 3, 2014, at 8:44 AM, Jorge Fábregas wrote:
> On 01/30/2014 09:02 PM, Jorge Fábregas wrote:
>> Now, here's the thing. I wanted to permanently run off these snapshots
>> so I wanted to delete the parent "subvolumes" for these snapshots (e.g.
>> "commit" the snapshot) by doing:
>>
>> # mou
On Jan 31, 2014, at 10:54 AM, Jorge Fábregas wrote:
>
> Ok, I might check that. All these years I've been using Clonezilla to
> do a "partition image" of my root filesystem before applying major
> updates. I have the ISO stored on my disk and GRUB2 is configured to
> boot ("loopback") this ima
On 01/30/2014 09:02 PM, Jorge Fábregas wrote:
> Now, here's the thing. I wanted to permanently run off these snapshots
> so I wanted to delete the parent "subvolumes" for these snapshots (e.g.
> "commit" the snapshot) by doing:
>
> # mount -o subvolid=5 /dev/vda3 /mnt
> # btrfs subvolume delete /
On 01/31/2014 10:51 AM, Neal Becker wrote:
> I filed this BR:
> https://bugzilla.redhat.com/show_bug.cgi?id=1060241
Thanks!
--
Jorge
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora
On 01/31/2014 12:29 AM, Chris Murphy wrote:
> FYI note the top level is 257 which is root subvolume, therefore this
> entry is the same as saying "top level 5 path root/yum_20140130172422"
Indeed. What a coincidence. The other day I was confused about what
"top level" meant and after searching
Chris Murphy wrote:
>
> On Jan 30, 2014, at 6:02 PM, Jorge Fábregas wrote:
>>
>> #btrfs subvolume list /
>> ID 257 gen 102 top level 5 path root
>> ID 258 gen 102 top level 5 path home
>> ID 278 gen 95 top level 257 path yum_20140130172422
>
> FYI note the top level is 257 which is root subvol
On Jan 30, 2014, at 6:02 PM, Jorge Fábregas wrote:
>
> #btrfs subvolume list /
> ID 257 gen 102 top level 5 path root
> ID 258 gen 102 top level 5 path home
> ID 278 gen 95 top level 257 path yum_20140130172422
FYI note the top level is 257 which is root subvolume, therefore this entry is
the
13 matches
Mail list logo
