[PATCH] xfstests: btrfs/004, fix failure with inlined file extents

2014-04-17 Thread Filipe David Borba Manana
Files that consist of an inline extent, have the corresponding data in the filesystem btree and not on a dedicated extent. For such extents filefrag (fiemap) will report a physical location of 0 for that extent and set the 'inline' flag. The btrfs inspect-internal logical-resolve command will caus

[PATCH] xfstests: btrfs/004, fix filefrag filter for files with 1 block only

2014-04-17 Thread Filipe David Borba Manana
If the file consists of a single block, then filefrag mentions '1 block of ...', and the filter expected 'blocks of ...'. Example: $ echo qwerty > foobar $ filefrag -v foobar Filesystem type is: ef53 File size of foobar is 7 (1 block of 4096 bytes) ext: logical_offset:physical_offset

Re: File changing in snapshot

2014-04-17 Thread Oliver O.
Am 17.04.2014 18:11, schrieb Oliver O.: Am 17.04.2014 17:56, schrieb Chris Mason: On 04/17/2014 11:39 AM, Oliver O. wrote: I seem to have observed a file on a (writable) snapshot changing although there were no writes occuring on the snapshot itself. This is not supposed to happen, right? W

Re: File changing in snapshot

2014-04-17 Thread Oliver O.
Am 17.04.2014 17:56, schrieb Chris Mason: On 04/17/2014 11:39 AM, Oliver O. wrote: I seem to have observed a file on a (writable) snapshot changing although there were no writes occuring on the snapshot itself. This is not supposed to happen, right? Was this a nodatacow file? -chris No. Mo

Re: File changing in snapshot

2014-04-17 Thread Chris Mason
On 04/17/2014 11:39 AM, Oliver O. wrote: I seem to have observed a file on a (writable) snapshot changing although there were no writes occuring on the snapshot itself. This is not supposed to happen, right? Sequence of events: 1. A (writable) snapshot @home-2014-04-16 is taken on a @home subvo

File changing in snapshot

2014-04-17 Thread Oliver O.
I seem to have observed a file on a (writable) snapshot changing although there were no writes occuring on the snapshot itself. This is not supposed to happen, right? Sequence of events: 1. A (writable) snapshot @home-2014-04-16 is taken on a @home subvolume mounted at /home. 2. The current

Re: filesystem hang when doing snapshot (3.15-rc1)

2014-04-17 Thread Tomasz Chmielewski
On Thu, 17 Apr 2014 10:24:32 +0800 Miao Xie wrote: > > scsi_request_fn+0x31/0x4dc [scsi_mod] [120462.559546] > > [] ? ktime_get_ts+0x50/0xb7 [120462.559594] > > [] ? delayacct_end+0x77/0x82 [120462.559641] > > [] ? __lock_page+0x63/0x63 [120462.559688] > > [] schedule+0x6a/0x6c [120462.559734] >