On 10/26/2011 07:25 PM, Helmut Hullen wrote:
Hallo, dima,
Du meintest am 26.10.11:
I'm trying to rm some files, this is what I get in dmesg:
[30975.249519] [ cut here ]
[30975.249529] WARNING: at fs/btrfs/extent-tree.c:4588
__btrfs_free_extent+0x3b7/0x7ed()
[...]
On 10/25/2011 01:48 PM, Kai Krakow wrote:
Hello list!
I'm trying to rm some files, this is what I get in dmesg:
[30975.249519] [ cut here ]
[30975.249529] WARNING: at fs/btrfs/extent-tree.c:4588
__btrfs_free_extent+0x3b7/0x7ed()
[30975.249532] Hardware name:
Hallo, dima,
Du meintest am 26.10.11:
I'm trying to rm some files, this is what I get in dmesg:
[30975.249519] [ cut here ]
[30975.249529] WARNING: at fs/btrfs/extent-tree.c:4588
__btrfs_free_extent+0x3b7/0x7ed()
[...]
[30975.249604] Pid: 12291, comm: rm Tainted:
Hello!
2011/10/26 dima dole...@parallels.com:
I'm trying to rm some files, this is what I get in dmesg:
[snip]
Can you ls the directory where the problem files are located? What would the
the output? I had a very similar problem but on 3.0.x kernel when several
files suddenly got corrupted.
Hallo, Kai,
Du meintest am 26.10.11:
I can run find -type f for directories I suspect corrupted files
in, and I see errors in dmesg if it happens to contain bad files. But
no oopses and the system remains stable. If I mount the filesystem
read-only I can even read these files without oopses,
On 10/27/2011 02:40 AM, Kai Krakow wrote:
I'm trying to rm some files, this is what I get in dmesg:
[snip]
Can you ls the directory where the problem files are located? What would the
the output? I had a very similar problem but on 3.0.x kernel when several
files suddenly got corrupted.
I
Hello list!
I'm trying to rm some files, this is what I get in dmesg:
[30975.249519] [ cut here ]
[30975.249529] WARNING: at fs/btrfs/extent-tree.c:4588
__btrfs_free_extent+0x3b7/0x7ed()
[30975.249532] Hardware name:
[30975.249535] Modules linked in: af_packet lm90
