Re: btrfsck errors is it save to fix?

2013-11-16 Thread Hendrik Friedel
Hello, Possible? Yes. Although I did not implicitly mention it, you would combine clear_cache and nospace_cache - that should do the trick. Then unmount and check. Thanks and mentally noted for further reference. I didn't think about combining the options, but it makes perfect sense now

Re: btrfsck errors is it save to fix?

2013-11-13 Thread Duncan
Kai Krakow posted on Tue, 12 Nov 2013 20:37:57 +0100 as excerpted: BTW, my first impression was that errors 400 means something like 400 errors - but that is just a hex bitmask which shows what errors have been found. So errors 100 is just _one_ bit set, thus only _one_ error. Same

Re: btrfsck errors is it save to fix?

2013-11-13 Thread Duncan
Kai Krakow posted on Tue, 12 Nov 2013 20:37:57 +0100 as excerpted: Possible? Yes. Although I did not implicitly mention it, you would combine clear_cache and nospace_cache - that should do the trick. Then unmount and check. Thanks and mentally noted for further reference. I didn't think

Re: btrfsck errors is it save to fix?

2013-11-12 Thread Kai Krakow
Duncan 1i5t5.dun...@cox.net schrieb: 100 is I_ERR_FILE_EXTENT_DISCOUNT. I'm not sure what kind of problem this indicates but btrfsck does not seem to fix this currently - it just detects it. Interesting... I wish it were documented what it technically means and what implications each

Re: btrfsck errors is it save to fix?

2013-11-11 Thread Hendrik Friedel
Hello, I re-post this: To answer the is it safe to fix question... In that context, yes, it's safe to btrfsck --repair, because you're prepared to lose the entire filesystem if worse comes to worse in any case, so even if btrfsck --repair makes things worse instead of better, you've not

Re: btrfsck errors is it save to fix?

2013-11-11 Thread Kai Krakow
Hendrik Friedel hend...@friedels.name schrieb: I re-post this: [...] root 256 inode 9579 errors 100 root 256 inode 9580 errors 100 root 256 inode 14258 errors 100 root 256 inode 14259 errors 100 root inode 9579 errors 100 root inode 9580 errors 100 root inode 14258 errors

Re: btrfsck errors is it save to fix?

2013-11-11 Thread Duncan
Kai Krakow posted on Tue, 12 Nov 2013 00:58:59 +0100 as excerpted: Hendrik Friedel hend...@friedels.name schrieb: I re-post this: [...] root 256 inode 9579 errors 100 root 256 inode 9580 errors 100 root 256 inode 14258 errors 100 root 256 inode 14259 errors 100 root inode 9579

Re: btrfsck errors is it save to fix?

2013-11-09 Thread Hendrik Friedel
Hello thanks for your reply. To answer the is it safe to fix question... In that context, yes, it's safe to btrfsck --repair, because you're prepared to lose the entire filesystem if worse comes to worse in any case, so even if btrfsck --repair makes things worse instead of better, you've

Re: btrfsck errors is it save to fix?

2013-11-08 Thread Duncan
Hendrik Friedel posted on Thu, 07 Nov 2013 20:16:34 +0100 as excerpted: can someone please help me on this? Your replies are upside down (reply before the quoted context in which it should be taken, edited to replied context as appropriate), so I've not included further quoted context. To

Re: btrfsck errors is it save to fix?

2013-11-07 Thread Hendrik Friedel
Hello again, can someone please help me on this? Regards, Hendrik Am 06.11.2013 07:45, schrieb Hendrik Friedel: Hello, sorry, I was totally unaware still being on 3.11rc2. I re-ran btrfsck with the same result: ./btrfs-progs/btrfsck /dev/sdc1 Checking filesystem on /dev/sdc1 UUID:

Re: btrfsck errors is it save to fix?

2013-11-05 Thread Hendrik Friedel
Hello, sorry, I was totally unaware still being on 3.11rc2. I re-ran btrfsck with the same result: ./btrfs-progs/btrfsck /dev/sdc1 Checking filesystem on /dev/sdc1 UUID: 989306aa-d291-4752-8477-0baf94f8c42f checking extents checking free space cache checking fs roots root 256 inode 9579 errors

Re: btrfsck errors is it save to fix?

2013-11-04 Thread Hendrik Friedel
Hello, the list was quite full with patches, so this might have been hidden. Here the complete Stack. Does this help? Is this what you needed? Greetings, Hendrik sorry about that: [ 126.444603] init: plymouth-stop pre-start process (3446) terminated with status 1 [11189.299864] hda-intel:

Re: btrfsck errors is it save to fix?

2013-11-04 Thread cwillu
On Mon, Nov 4, 2013 at 3:14 PM, Hendrik Friedel hend...@friedels.name wrote: Hello, the list was quite full with patches, so this might have been hidden. Here the complete Stack. Does this help? Is this what you needed? [95764.899294] CPU: 1 PID: 21798 Comm: umount Tainted: GFCIO

Re: btrfsck errors is it save to fix?

2013-11-02 Thread cwillu
Now that I am searching, I see this in dmesg: [95764.899359] [a00d9a59] free_fs_root+0x99/0xa0 [btrfs] [95764.899384] [a00dd653] btrfs_drop_and_free_fs_root+0x93/0xc0 [btrfs] [95764.899408] [a00dd74f] del_fs_roots+0xcf/0x130 [btrfs] [95764.899433]

Re: btrfsck errors is it save to fix?

2013-11-02 Thread Hendrik Friedel
Hello, sorry about that: [ 126.444603] init: plymouth-stop pre-start process (3446) terminated with status 1 [11189.299864] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. [94999.489736] device fsid 989306aa-d291-4752-8477-0baf94f8c42f devid 2 transid

btrfsck errors is it save to fix?

2013-11-01 Thread Hendrik Friedel
Hello, I have noticed that my server experiences high load average when writing to it. So I checked the file-system and found errors: ./btrfsck /dev/sdc1 Checking filesystem on /dev/sdc1 UUID: 989306aa-d291-4752-8477-0baf94f8c42f checking extents checking free space cache checking fs roots