Re: Ideas to do custom operation just after mount?

Am Mon, 21 Dec 2015 13:18:22 +0800 schrieb Anand Jain : > > > > BTW, any good idea for btrfs to do such operation like > > enabling/disabling some minor features? Especially when it can be > > set on individual file/dirs. > > > > Features like incoming write time

Re: btrfs check inconsistency with raid1, part 1

Am Mon, 21 Dec 2015 10:23:31 +0800 schrieb Qu Wenruo : > > > Chris Murphy wrote on 2015/12/20 19:12 -0700: > > On Sun, Dec 20, 2015 at 6:43 PM, Qu Wenruo > > wrote: > >> > >> > >> Chris Murphy wrote on 2015/12/20 15:31 -0700: > > > >>> I think

[GIT PULL] Btrfs bug fixes for 4.5

From: Filipe Manana Hi Chris, Please consider the following fixes for the 4.5 merge window. Nothing outstanding, they are just the usual bug fixes (races, deadlocks, error paths, etc). These were all sent previously to the mailing list and rebased last week against your

Re: defrag vs autodefrag

On Sun, Dec 20, 2015 at 07:26:07PM -0600, Donald Pearson wrote: > I read an implication in a different thread that defrag and autodefrag > behave differently in that autodefrag is more snapshot friendly for > COW data. > > Did I understand that correctly? I have not been doing defrag on my >

Re: dear developers, can we have notdatacow + checksumming, plz?

On 2015-12-16 21:09, Christoph Anton Mitterer wrote: On Tue, 2015-12-15 at 11:00 -0500, Austin S. Hemmelgarn wrote: Well sure, I think we'de done most of this and have dedicated controllers, at least of a quality that funding allows us ;-) But regardless how much one tunes, and how good the

Re: [GIT PULL] Btrfs bug fixes for 4.5

On Mon, Dec 21, 2015 at 05:59:46PM +, fdman...@kernel.org wrote: > From: Filipe Manana > > Hi Chris, > > Please consider the following fixes for the 4.5 merge window. > Nothing outstanding, they are just the usual bug fixes (races, deadlocks, > error paths, etc). These

Re: attacking btrfs filesystems via UUID collisions?

Am Thu, 17 Dec 2015 03:25:50 + (UTC) schrieb Duncan <1i5t5.dun...@cox.net>: > So it's definitely _not_ something that reiserfsck would do in a > "normal" fsck, only when doing "I'm desperate and don't have backups, > go to the ends of the earth if necessary to recover what you can of > my

Re: btrfs check inconsistency with raid1, part 1

Am Tue, 22 Dec 2015 09:22:20 +0800 schrieb Qu Wenruo : > > > Kai Krakow wrote on 2015/12/22 02:05 +0100: > > Am Mon, 21 Dec 2015 10:23:31 +0800 > > schrieb Qu Wenruo : > > > >> > >> > >> Chris Murphy wrote on 2015/12/20 19:12 -0700: > >>> On

[PATCH v4 2/2] btrfs: Introduce new mount option to disable tree log replay

Introduce a new mount option "nologreplay" to co-operate with "ro" mount option to get real readonly mount, like "norecovery" in ext* and xfs. Since the new parse_options() need to check new flags at remount time, so add a new parameter for parse_options(). Signed-off-by: Qu Wenruo

Re: btrfs check inconsistency with raid1, part 1

Kai Krakow wrote on 2015/12/22 02:48 +0100: Am Tue, 22 Dec 2015 09:22:20 +0800 schrieb Qu Wenruo : Kai Krakow wrote on 2015/12/22 02:05 +0100: Am Mon, 21 Dec 2015 10:23:31 +0800 schrieb Qu Wenruo : Chris Murphy wrote on 2015/12/20

[PATCH v4 1/2] btrfs: Introduce new mount option backuproot to replace recovery

Current "recovery" mount option will only try to use backup root. However the word "recovery" is too generic and may be confusing for some users. Here introduce a new and more specific mount option, "backuproot" to replace "recovery" mount option. "Recovery" will be kept for compatibility reason,

Re: btrfs check inconsistency with raid1, part 1

Latest update. 4.4.0-0.rc6.git0.1.fc24.x86_64 btrfs-progs v4.3.1 Mounted the volume normally with both devices available, no mount options, so it is a rw mount. And it mounts with only the normal kernel messages: [ 9458.290778] BTRFS info (device sdc): disk space caching is enabled [

Re: btrfs check inconsistency with raid1, part 1

Kai Krakow wrote on 2015/12/22 02:05 +0100: Am Mon, 21 Dec 2015 10:23:31 +0800 schrieb Qu Wenruo : Chris Murphy wrote on 2015/12/20 19:12 -0700: On Sun, Dec 20, 2015 at 6:43 PM, Qu Wenruo wrote: Chris Murphy wrote on 2015/12/20 15:31

Re: safety of journal based fs (was: Re: still kworker at 100% cpu…)

Am Mon, 14 Dec 2015 10:10:51 +0100 schrieb Martin Steigerwald : > > But the problem is, when recovering journal, there is no journal of > > journal, to keep journal recovering safe from power loss. > > But the journal should be safe due to a journal commit being one >

kernel BUG at /home/kernel/COD/linux/fs/btrfs/volumes.c:5508

Hi guys, Have a nasty issue to report here. I have a RAID10 btrfs configuration where I was replacing one disk for another. Unfortunately, during the replace, it seems like one of my disks (not in the array) stopped getting powered (looks like the cable was loose) and caused the machine to

Re: compression disk space saving - what are your results?

Am Wed, 2 Dec 2015 09:49:05 -0500 schrieb Austin S Hemmelgarn : > > So, 138 GB files use just 24 GB on disk - nice! > > > > However, I would still expect that compress=zlib has almost the same > > effect as compress-force=zlib, for 100% text files/logs. > > > That's better

Re: defrag vs autodefrag

On Mon, Dec 21, 2015 at 8:14 AM, Hugo Mills wrote: > On Sun, Dec 20, 2015 at 07:26:07PM -0600, Donald Pearson wrote: >> I read an implication in a different thread that defrag and autodefrag >> behave differently in that autodefrag is more snapshot friendly for >> COW data. >>

Re: Ideas on unified real-ro mount option across all filesystems

Am Fri, 18 Dec 2015 03:01:06 +0100 schrieb Christoph Anton Mitterer : > The manpage says: > > ro Mount the filesystem read-only. > > rw Mount the filesystem read-write. That means: the filesystem... Not the block device... Sorry, it's kinda nitpicking. But

[PATCH 3/3 v2] btrfs: use list_for_each_entry* in backref.c

Use list_for_each_entry*() to simplify the code. Signed-off-by: Geliang Tang --- Changes in v2: - Use list_for_each_entry_safe_continue() in __merge_refs(). --- fs/btrfs/backref.c | 23 ++- 1 file changed, 6 insertions(+), 17 deletions(-) diff --git