https://bugzilla.novell.com/show_bug.cgi?id=838475 https://bugzilla.novell.com/show_bug.cgi?id=838475#c1 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |Kernel AssignedTo|werner@suse.com |kernel-maintainers@forge.pr | |ovo.novell.com --- Comment #1 from Dr. Werner Fink 2013-09-05 06:45:30 UTC --- IMHO systemd + journald is the reporter as well as affected by the misbehaviour of the BtrFS but not the cause. Otherwise it would also happen with other file systems as well. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=838475 https://bugzilla.novell.com/show_bug.cgi?id=838475#c4 --- Comment #4 from Frederic Crozat 2013-09-06 09:12:12 UTC --- using journal storage on disk is probably the culprit: any queries done with journalctl (or even systemctl status, since it will query the journal) will cause systemd-journald to entirely read and parse journal from disk, which can be easily several hundred MB, before doing any output on screen. I've discussed this issue with upstream but I doubt they'll be able to improve it much, due to the on-disk format used by journal (it is some kind of database). I can't really comment on performance difference between btrfs and ext3/4 for journal, because all my 12.3/Factory systems are running with btrfs ;) It would be interesting to install a physical system with exactly the same setup, both in btrfs and ext3/4, enable journal on disk (install systemd-logger package), reboot several time to ensure the journal on disk is become big (200 to 300MB) and then test IO output on it. Maybe journal on disk is also getting easily fragmented with CoW (just a guess) which could explain bad performance on btrfs (but again, I don't have any hard evidence to prove this) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=838475 https://bugzilla.novell.com/show_bug.cgi?id=838475#c7 --- Comment #7 from Gábor Nyers 2013-09-17 09:34:33 UTC --- Could someone recommend some test which might help pinpoint the problem here? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=838475 https://bugzilla.novell.com/show_bug.cgi?id=838475#c9 --- Comment #9 from Gábor Nyers 2013-09-17 15:48:05 UTC --- The long version is 42 klines long, if you need it I could attach it to this bug. This is the excerpt: # filefrag -vbs /var/log/journal/*/*| grep var File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system.journal is 10260480 (10020 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system.journal: 1972 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@0004e3dacc21fda1-53f2f5d494bb7bf6.journal~ is 2158592 (2108 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@0004e3dacc21fda1-53f2f5d494bb7bf6.journal~: 454 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@0004e5c7620ea37b-53c704bdd3e3f2fd.journal~ is 15552512 (15188 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@0004e5c7620ea37b-53c704bdd3e3f2fd.journal~: 3083 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@0004e5e53e349a84-dad3174f56d7d1ae.journal~ is 5988352 (5848 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@0004e5e53e349a84-dad3174f56d7d1ae.journal~: 1245 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@15d1a2f6d3f04af2802937e6ca056c90-0000000000006ab1-0004e282926c5913.journal is 14458880 (14120 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@15d1a2f6d3f04af2802937e6ca056c90-0000000000006ab1-0004e282926c5913.journal: 2990 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@15d1a2f6d3f04af2802937e6ca056c90-000000000000b701-0004e2de75571153.journal is 15691776 (15324 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@15d1a2f6d3f04af2802937e6ca056c90-000000000000b701-0004e2de75571153.journal: 3002 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@15d1a2f6d3f04af2802937e6ca056c90-0000000000010eee-0004e36078c29393.journal is 15765504 (15396 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@15d1a2f6d3f04af2802937e6ca056c90-0000000000010eee-0004e36078c29393.journal: 3344 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@4702a56f33ac446bbb65cdd754013b70-0000000000000001-0004e5e53a2ecfeb.journal is 16429056 (16044 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@4702a56f33ac446bbb65cdd754013b70-0000000000000001-0004e5e53a2ecfeb.journal: 3297 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@4702a56f33ac446bbb65cdd754013b70-0000000000005b72-0004e617b778c97c.journal is 15679488 (15312 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@4702a56f33ac446bbb65cdd754013b70-0000000000005b72-0004e617b778c97c.journal: 3051 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@fe792ec607664551879ec5e7f6eed3e6-0000000000000001-0004e3dac84d80d9.journal is 16596992 (16208 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@fe792ec607664551879ec5e7f6eed3e6-0000000000000001-0004e3dac84d80d9.journal: 3322 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@fe792ec607664551879ec5e7f6eed3e6-0000000000006072-0004e42bfbde6c28.journal is 16326656 (15944 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@fe792ec607664551879ec5e7f6eed3e6-0000000000006072-0004e42bfbde6c28.journal: 3538 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@fe792ec607664551879ec5e7f6eed3e6-000000000000be79-0004e48ad52ae190.journal is 16080896 (15704 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@fe792ec607664551879ec5e7f6eed3e6-000000000000be79-0004e48ad52ae190.journal: 3308 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@fe792ec607664551879ec5e7f6eed3e6-0000000000011743-0004e501b410b236.journal is 15794176 (15424 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@fe792ec607664551879ec5e7f6eed3e6-0000000000011743-0004e501b410b236.journal: 3329 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@fe792ec607664551879ec5e7f6eed3e6-0000000000016f6c-0004e550b46a83ed.journal is 14692352 (14348 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/system@fe792ec607664551879ec5e7f6eed3e6-0000000000016f6c-0004e550b46a83ed.journal: 2940 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000.journal is 950272 (928 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000.journal: 200 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@0004e3dad2306870-051935090da5f126.journal~ is 765952 (748 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@0004e3dad2306870-051935090da5f126.journal~: 123 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@0004e5b72ee2fc04-8705a6591bea6eef.journal~ is 1110016 (1084 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@0004e5b72ee2fc04-8705a6591bea6eef.journal~: 242 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@0004e5c76a3aacc3-c76964953f963080.journal~ is 806912 (788 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@0004e5c76a3aacc3-c76964953f963080.journal~: 161 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@0004e5e580995c7d-dbf44af9509134f1.journal~ is 774144 (756 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@0004e5e580995c7d-dbf44af9509134f1.journal~: 114 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@15d1a2f6d3f04af2802937e6ca056c90-0000000000000608-0004e1c8f12fc09c.journal is 1359872 (1328 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@15d1a2f6d3f04af2802937e6ca056c90-0000000000000608-0004e1c8f12fc09c.journal: 220 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@15d1a2f6d3f04af2802937e6ca056c90-0000000000006afb-0004e282bd555f62.journal is 1052672 (1028 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@15d1a2f6d3f04af2802937e6ca056c90-0000000000006afb-0004e282bd555f62.journal: 229 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@15d1a2f6d3f04af2802937e6ca056c90-000000000000b82d-0004e2de9e36e086.journal is 1294336 (1264 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@15d1a2f6d3f04af2802937e6ca056c90-000000000000b82d-0004e2de9e36e086.journal: 192 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@15d1a2f6d3f04af2802937e6ca056c90-0000000000011018-0004e36097e3c25f.journal is 1306624 (1276 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@15d1a2f6d3f04af2802937e6ca056c90-0000000000011018-0004e36097e3c25f.journal: 281 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@4702a56f33ac446bbb65cdd754013b70-0000000000000679-0004e5e580a014f8.journal is 1224704 (1196 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@4702a56f33ac446bbb65cdd754013b70-0000000000000679-0004e5e580a014f8.journal: 253 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@4702a56f33ac446bbb65cdd754013b70-0000000000005be1-0004e617c4777c1f.journal is 1265664 (1236 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@4702a56f33ac446bbb65cdd754013b70-0000000000005be1-0004e617c4777c1f.journal: 236 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@fe792ec607664551879ec5e7f6eed3e6-000000000000060f-0004e3dad2351ed4.journal is 1196032 (1168 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@fe792ec607664551879ec5e7f6eed3e6-000000000000060f-0004e3dad2351ed4.journal: 255 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@fe792ec607664551879ec5e7f6eed3e6-00000000000062b4-0004e42ce32b8539.journal is 1216512 (1188 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@fe792ec607664551879ec5e7f6eed3e6-00000000000062b4-0004e42ce32b8539.journal: 265 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@fe792ec607664551879ec5e7f6eed3e6-000000000000bef8-0004e48b6980140c.journal is 1241088 (1212 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@fe792ec607664551879ec5e7f6eed3e6-000000000000bef8-0004e48b6980140c.journal: 260 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@fe792ec607664551879ec5e7f6eed3e6-0000000000011776-0004e501b80aa16d.journal is 1056768 (1032 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@fe792ec607664551879ec5e7f6eed3e6-0000000000011776-0004e501b80aa16d.journal: 218 extents found File size of /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@fe792ec607664551879ec5e7f6eed3e6-0000000000017279-0004e561fcd3a041.journal is 1114112 (1088 blocks, blocksize 1024) /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/user-1000@fe792ec607664551879ec5e7f6eed3e6-0000000000017279-0004e561fcd3a041.journal: 251 extents found -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=838475 https://bugzilla.novell.com/show_bug.cgi?id=838475#c Alberto Planas Dominguez changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| | SILVER -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=838475 https://bugzilla.novell.com/show_bug.cgi?id=838475#c12 --- Comment #12 from Gábor Nyers 2013-10-03 22:50:26 UTC --- (In reply to comment #11) On a related note: As an alternative to moving the /var to some other filesystem, I've also tried to disable CoW for journald's files with: # chattr +C /var/log/journal/3e*/* This has not resulted in error, however: # lsattr * returns no C attributes set. I'd have expected something like this: # lsattr system.journal ---------------C system.journal instead I get: # lsattr system.journal ---------------- system.journal Could someone confirm that this is an unexpected behavior? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=838475 https://bugzilla.novell.com/show_bug.cgi?id=838475#c16 --- Comment #16 from Gábor Nyers 2013-10-04 13:16:28 UTC --- (In reply to comment #13) Whether or not some process holds an open file descriptor has no effect on the ability to set the "C" attribute. Instead, the warning of the 'chattr' man page appears to be relevant here:

A file with the 'C' attribute set will not be subject to copy-on- write updates. This flag is only supported on file systems which perform copy-on-write. (Note: For btrfs, the 'C' flag should be set on new or empty files. If it is set on a file which already has data blocks, it is undefined when the blocks assigned to the file will be fully stable. If the 'C' flag is set on a directory, it will have no effect on the directory, but new files created in that directory will the No_COW attribute.)

Would be interesting to know the reason... incomplete implementation or a more fundamental problem? Anyway, I tried and can confirm. Also, a way to shortcut the need to flag files individually with the "C" attribute would be to do this on the directory. All newly created files will inherit it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=838475 https://bugzilla.novell.com/show_bug.cgi?id=838475#c17 David Sterba changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dsterba@suse.com --- Comment #17 from David Sterba 2013-11-25 18:34:54 CET --- (In reply to comment #16)

...

A file with the 'C' attribute set will not be subject to copy-on- write updates. This flag is only supported on file systems which perform copy-on-write. (Note: For btrfs, the 'C' flag should be set on new or empty files. If it is set on a file which already has data blocks, it is undefined when the blocks assigned to the file will be fully stable. If the 'C' flag is set on a directory, it will have no effect on the directory, but new files created in that directory will the No_COW attribute.)

Would be interesting to know the reason... incomplete implementation or a more fundamental problem? Anyway, I tried and can confirm.

It's a compromise to keep the implementation sane with the same guarantees. Making any existing file nocow is possible in theory, but the transition would need to be fully crash safe and keeping the intermediate status would need incompatible changes.

Also, a way to shortcut the need to flag files individually with the "C" attribute would be to do this on the directory. All newly created files will inherit it.

This should work for the journal files. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=838475 https://bugzilla.novell.com/show_bug.cgi?id=838475#c19 --- Comment #19 from Dr. Werner Fink 2013-11-26 10:11:02 UTC --- @ Davi and Gabor ... is there anything which can be done by systemd like a special file dexscriptor flag to avoid or reduce this problem? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=838475 https://bugzilla.novell.com/show_bug.cgi?id=838475#c21 --- Comment #21 from Frederic Crozat 2013-12-06 10:55:44 UTC --- my only suggestion would be to set +C attribute on /var/log/journal, to flag it as nocow. But I'm not 100% sure it will improve the performance (I can't test anymore on my main system which is now running with SSD, so almost zero latency when accessing journal) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=838475 https://bugzilla.novell.com/show_bug.cgi?id=838475#c23 Matthias Eckermann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@suse.com --- Comment #23 from Matthias Eckermann 2013-12-06 11:21:38 UTC --- Why don't we just set "+C" on /var/log/ in general, if we are running on btrfs? In that case, /var/log/ is a subvolume of its own anyways, and its unlikely that someone wants to snapshot and rollback this directory, as this would violate compliance (that's why it is a subvolume of its own: minimize risk). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=838475 https://bugzilla.novell.com/show_bug.cgi?id=838475#c25 --- Comment #25 from Dr. Werner Fink 2013-12-06 12:35:41 UTC --- Created an attachment (id=570612) --> (http://bugzilla.novell.com/attachment.cgi?id=570612) 1015-journald-with-journaling-FS.patch This I suppose should fix the bottlenet hopefully -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=838475 https://bugzilla.novell.com/show_bug.cgi?id=838475#c28 --- Comment #28 from Dr. Werner Fink 2013-12-10 16:16:11 UTC --- Can anyone test the latest systemd out? I've no BtrFS around here nevertheless I's like to submit this patch in a similar to upstream -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=838475 https://bugzilla.novell.com/show_bug.cgi?id=838475#c30 --- Comment #30 from David Sterba 2013-12-10 17:46:45 CET --- Patch from comment #25 looks good, I've verified that the flags are inherited to newly created dirs and files. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=838475 https://bugzilla.novell.com/show_bug.cgi?id=838475#c32 --- Comment #32 from Gábor Nyers 2013-12-12 09:45:04 UTC --- (In reply to comment #31)

I don't understand what's the concern in comment 18. Newly created files can be set NOCOW or inherit that flag from the directory, that's been mentioned already and that's what the proposed patch will ensure.

Please be more specific what did not work for you on 12.3.

Sure, let's give it another try. The point in comment #18 is that (at least in my case) setting the NoCoW attribute did not had an effect on the fragmentation and as I suspect (based on some tests with cloning a file and overwriting 1 clone) the CoW behavior of Btrfs. To be specific: I've had the '+C' attribute on the /var/log/journal/*/* directories and files for months now and the journal fragments like crazy: # cd /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/ # filefrag * | sort -nk 2 | tail -10 user-1000.journal: 72 extents found user-1000@d7a2dfbcebfc44dca3cdc8f77e78260e-0000000000054e42-0004ecc95eda51ee.journal: 187 extents found user-1000@d7a2dfbcebfc44dca3cdc8f77e78260e-000000000005e101-0004ed1c2aa242d6.journal: 204 extents found user-1000@d7a2dfbcebfc44dca3cdc8f77e78260e-00000000000597c6-0004ed020f1b176a.journal: 223 extents found user-1000@d7a2dfbcebfc44dca3cdc8f77e78260e-000000000006273c-0004ed304ec0db9c.journal: 223 extents found system.journal: 560 extents found system@d7a2dfbcebfc44dca3cdc8f77e78260e-0000000000062618-0004ed30101d2b2c.journal: 2975 extents found system@d7a2dfbcebfc44dca3cdc8f77e78260e-0000000000054e13-0004ecc94e42a2ab.journal: 3015 extents found system@d7a2dfbcebfc44dca3cdc8f77e78260e-000000000005e0b2-0004ed1c0f9d9a8e.journal: 3077 extents found system@d7a2dfbcebfc44dca3cdc8f77e78260e-0000000000059773-0004ed01fec7bb9d.journal: 3096 extents found This level of fragmentation is just after a few days of having done a `btrfs file defrag /var/log/journal/3e9b548e87a6e6e3afed740e000003c5/* So I'd say that there is some empirical evidence suggesting that changing Btrfs NoCoW behavior is not trivial. I've raised this issue to Jeff in a private mail and I've quoted above statement from his response. Maybe he could elaborate more on this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=838475 https://bugzilla.novell.com/show_bug.cgi?id=838475#c Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |856067 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=838475 https://bugzilla.novell.com/show_bug.cgi?id=838475#c36 --- Comment #36 from Dr. Werner Fink 2013-12-18 14:42:33 UTC --- (In reply to comment #35) Hmm ... it is clear that FS_NOCOW_FL works only for *new* created files. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=838475 https://bugzilla.novell.com/show_bug.cgi?id=838475#c Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- OS/Version|Other |openSUSE 12.3 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=838475 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|SILVER |SILVER |obs:running:4038:moderate | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=838475 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|SILVER |SILVER |obs:running:4416:moderate | -- You are receiving this mail because: You are on the CC list for the bug.