Re: chmod errors compiling on btrfs

On Mon, Nov 09, 2009 at 06:58:07PM +, Andrew Benton wrote: > On 09/11/09 15:15, Chris Mason wrote: > >We fixed some umask problems recently, these should be fixed in the > >master branch of the btrfs-unstable repo (which is against 2.6.31). > > > > Thanks, that did the trick. Will these umask

Re: chmod errors compiling on btrfs

On 09/11/09 15:15, Chris Mason wrote: We fixed some umask problems recently, these should be fixed in the master branch of the btrfs-unstable repo (which is against 2.6.31). Thanks, that did the trick. Will these umask fixes be in the 2.6.32 kernel? Andy -- To unsubscribe from this list: send

Re: chmod errors compiling on btrfs

On 09/11/09 15:15, Chris Mason wrote: On Sat, Nov 07, 2009 at 08:36:40PM +, Andrew Benton wrote: Both times the files created were world writeable when they should have been read only. I get the same errors if I compile as myself or root. If I compile in my home folder (on a reiserfs partit

Re: rootfs snapshots and rollback (i.e. testing updates)

Hi, > Is it possible, with current btrfs: Yes, I think so. > - to take a rootfs snapshot (i.e. prior to a major update), btrfsctl -s newsnap / > - do changes in the root filesystem (i.e. install major update), > > - if we don't like what the major update did to the system >

Re: rootfs snapshots and rollback (i.e. testing updates)

Hi, I asked this question about a month ago, and the answer is roughly "It's theoretically possible with minor feature implementations to btrfs, though nobody's done it yet" On Nov 9, 2009, at 10:00 AM, Tomasz Chmielewski wrote: Is it possible, with current btrfs: - to take a rootfs snaps

Re: chmod errors compiling on btrfs

On Sat, Nov 07, 2009 at 08:36:40PM +, Andrew Benton wrote: > > Both times the files created were world writeable when they should > have been read only. I get the same errors if I compile as myself or > root. If I compile in my home folder (on a reiserfs partition) they > compile with no probl

rootfs snapshots and rollback (i.e. testing updates)

Is it possible, with current btrfs: - to take a rootfs snapshot (i.e. prior to a major update), - do changes in the root filesystem (i.e. install major update), - if we don't like what the major update did to the system (rootfs), "rollback" the snapshot and make it the "original" rootfs again

Re: [PATCH] Prevent btrfsck to run on mounted filesystems

Hi! > > In this case O_EXCL is going to be more accurate just because the > > mounted check doesn't cover every disk in the FS. For now btrfsck > > doesn't really give consistent results even readonly on a mounted > > filesystem. We should prevent it with a message just to prevent > > confusion.