btrfs check bug

2017-04-18 Thread Jan Koester
Hi, i have to try to create a new extent-tree after checksum error not solveable with srub or init-csum-tree. Now i got this failure output from btrfs --repair:   ERROR: errors found in extent allocation tree or chunk allocation Fixed 0 roots. checking free space cache checking fs roots root 5

Re: mounting failed any file on my filesystem

2017-01-01 Thread Jan Koester
On Samstag, 31. Dezember 2016 05:05:03 CET Duncan wrote: > Jan Koester posted on Fri, 30 Dec 2016 13:17:37 +0100 as excerpted: > > sudo btrfs filesystem df /mnt > > Data, RAID6: total=1.22TiB, used=0.00B > > System, RAID6: total=96.00MiB, used=0.00B > > Metadata,

Re: mounting failed any file on my filesystem

2016-12-30 Thread Jan Koester
On Donnerstag, 29. Dezember 2016 22:31:29 CET Duncan wrote: > Jan Koester posted on Thu, 29 Dec 2016 20:05:35 +0100 as excerpted: > > Hi, > > > > i have problem with filesystem if my system crashed i have made been > > hard reset of the system after my Filesystem

mounting failed any file on my filesystem

2016-12-29 Thread Jan Koester
Hi, i have problem with filesystem if my system crashed i have made been hard reset of the system after my Filesystem was crashed. I have already tried to repair without success you can see it on log file. It's seem one corrupted block brings complete filesystem to crashing. Have anybody idea

chunk recover segfault

2016-11-12 Thread Jan Koester
Hi, got segault if i run rescue chunk-recover. My Kernel: Linux dibsi 4.9.0-040900rc2-generic #201610232131 SMP Mon Oct 24 01:32:49 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux btrfs Progs: btrfs-progs v4.8.3 gdb ouput btrfs rescue chunk-recover: Starting program: /home/jan/btrfs-progs/btrfs

Re: mount error raid6

2016-10-28 Thread Jan Koester
On Sonntag, 25. September 2016 11:25:40 CEST you wrote: > Hi, > > i got some errors in dmesg if i want to mount my Filesystem, > > uname -a: > Linux dibsi 4.8.0-040800rc7-generic #201609182130 SMP Mon Sep 19 01:32:13 > UTC 2016 x86_64 x86_64 x86_64 GNU/Linux > > dmesg: > [ 71.599464] BTRFS

Re: segfault btrfs scrub

2016-09-10 Thread Jan Koester
found FC3DF84D wanted 2164EB93 checksum verify failed on 2280458502144 found FC3DF84D wanted 2164EB93 bytenr mismatch, want=2280458502144, have=15938383240448 Am 10.09.2016 um 13:55 schrieb Jan Koester: Hi, i have now installed kernel 4.8-rc5 now i got this output when i starting scrub. My

Re: segfault btrfs scrub

2016-09-10 Thread Jan Koester
at 02:41:45PM +0200, Jan Koester wrote: Hi, i got from btrfs scrub command segfault. I use btrfs tools 4.7.2. root@dibsi:/home/jan# btrfs scrub status /local Speicherzugriffsfehler root@dibsi:/home/jan# dmesg [78294.556713] BTRFS error (device sda): bad tree block start 18427384836265136347

Re: segfault btrfs scrub

2016-09-10 Thread Jan Koester
at 02:41:45PM +0200, Jan Koester wrote: Hi, i got from btrfs scrub command segfault. I use btrfs tools 4.7.2. root@dibsi:/home/jan# btrfs scrub status /local Speicherzugriffsfehler root@dibsi:/home/jan# dmesg [78294.556713] BTRFS error (device sda): bad tree block start 18427384836265136347

segfault btrfs scrub

2016-09-09 Thread Jan Koester
    Hi, i got from btrfs scrub command segfault. I use btrfs tools 4.7.2.   root@dibsi:/home/jan# btrfs scrub status /local Speicherzugriffsfehler root@dibsi:/home/jan# dmesg [78294.556713] BTRFS error (device sda): bad tree block start 18427384836265136347 2304683610112 [78294.556956] BTRFS

cannot repair raid6 volume rescue zero-log crashed

2016-02-27 Thread Jan Koester
Hi,   cannot recover my home filesystem.   Linux dibsi 4.2.0-30-generic #35-Ubuntu SMP Fri Feb 19 13:52:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux   btrfs --version btrfs-progs v4.4 btrfs fi show Label: 'root' uuid: 3d279e92-d021-4a57-92b8-db3bfcbba79d Total devices 1 FS bytes used

cannot repair filesystem

2016-01-01 Thread Jan Koester
Hi, if I try to repair filesystem got I'am assert. I use Raid6. Linux dibsi 3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.7-ckt4-3~bpo70+1 (2015-02-12) x86_64 GNU/Linux root@dibsi:~/btrfs-progs# btrfs fi show Label: none uuid: 6a2f3936-d0ef-43c0-9815-41e24f2bc21a Total devices 1 FS bytes