Re: Crashed filesystem, nothing helps

2017-08-07 Thread Henk Slager
On Mon, Aug 7, 2017 at 7:12 AM, Thomas Wurfbaum wrote: > Now i do a btrfs-find-root, but it runs now since 5 day without a result. > How long should i wait? Or is it already to late to hope? > > mainframe:~ # btrfs-find-root.static /dev/sdb1 > parent transid verify failed on

Re: Crashed filesystem, nothing helps

2017-08-06 Thread Thomas Wurfbaum
Now i do a btrfs-find-root, but it runs now since 5 day without a result. How long should i wait? Or is it already to late to hope? mainframe:~ # btrfs-find-root.static /dev/sdb1 parent transid verify failed on 29376512 wanted 1327723 found 1489835 parent transid verify failed on 29376512 wanted

Re: Crashed filesystem, nothing helps

2017-08-02 Thread Thomas Wurfbaum
With the help of btrfs-corrupt-block i was able to get a little bit farer. I marked some of my problem block corrupt. Now i am in this stage mainframe:~ # btrfs restore /dev/sdb1 /mnt parent transid verify failed on 29409280 wanted 1486829 found 1488801 parent transid verify failed on 29409280

Re: Crashed filesystem, nothing helps

2017-08-02 Thread Thomas Wurfbaum
Am Mittwoch, 2. August 2017, 11:31:41 CEST schrieb Roman Mamedov: > Did it just abruptly exit there? Or you terminated it? It apruptly stopped there Regards, Thomas -- Thomas Wurfbaum Starkertshofen 15 85084 Reichertshofen Tel.: +49-160-3696336 Mail: tho...@wurfbaum.net

Re: Crashed filesystem, nothing helps

2017-08-02 Thread Roman Mamedov
On Wed, 02 Aug 2017 11:17:04 +0200 Thomas Wurfbaum wrote: > A restore does also not help: > mainframe:~ # btrfs restore /dev/sdb1 /mnt > parent transid verify failed on 29392896 wanted 1486833 found 1486836 > parent transid verify failed on 29392896 wanted 1486833 found

Re: Crashed filesystem, nothing helps

2017-08-02 Thread Thomas Wurfbaum
Maybe you are right, but i just followed the Suse guide: https://en.opensuse.org/SDB:BTRFS How to repair a broken/unmountable btrfs filesystem I already tried the commands mount with the -o usebackuproot option. (And -o usebackuproot,ro as well) But they just produce this in dmesg:

Re: Crashed filesystem, nothing helps

2017-08-02 Thread Hugo Mills
On Wed, Aug 02, 2017 at 10:27:50AM +0200, Thomas Wurfbaum wrote: > Hello, > > Yesterday morning i recognized a hard reboot of my system, but the /data > filesystem was > not possible to mount. > > > mainframe:~ # uname -a > Linux mainframe 4.11.8-2-default #1 SMP PREEMPT Thu Jun 29 14:37:33

Re: Crashed filesystem, nothing helps

2017-08-02 Thread Thomas Wurfbaum
Please find attached my dmesg.log Regards, Thomas[0.00] Linux version 4.11.8-2-default (geeko@buildhost) (gcc version 7.1.1 20170629 [gcc-7-branch revision 249772] (SUSE Linux) ) #1 SMP PREEMPT Thu Jun 29 14:37:33 UTC 2017 (42bd7a0) [0.00] Command line:

Crashed filesystem, nothing helps

2017-08-02 Thread Thomas Wurfbaum
Hello, Yesterday morning i recognized a hard reboot of my system, but the /data filesystem was not possible to mount. mainframe:~ # uname -a Linux mainframe 4.11.8-2-default #1 SMP PREEMPT Thu Jun 29 14:37:33 UTC 2017 (42bd7a0) x86_64 x86_64 x86_64 GNU/Linux mainframe:~ # btrfs --version