Re: BTRFS partition corrupted after deleting files in /home

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jan 12, 2021 at 12:24 AM Sreyan Chakravarty <sreyan32@xxxxxxxxx> wrote:
>
> On Sat, Jan 9, 2021 at 11:55 AM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote:
> >
> >
> >  So thanks
> > for not giving up.
> >
>
> Actually it is me who should be thanking you for not giving up.
>
> For me giving up was not an option since that would involve me losing
> all my data.
>
> Thank you again for your time and patience, others would have told me
> to reinstall my OS or restore my backups.
>
>
> > sudo dnf install
> > https://download.copr.fedorainfracloud.org/results/ngompa/btrfsprogs-robustimg/fedora-33-x86_64/01873195-btrfs-progs/btrfs-progs-5.9+git20210108.3783313-0.fc33.1.x86_64.rpm
> >
>
> Ok, I finally have some good news and some minor bad news hopefully.
>
> Good news first.
>
> It worked, I can now mount my BTRFS root file system:
>
> # mount -t btrfs /dev/mapper/dm_crypt /mnt/
> # ll /mnt
> # total 0
> drwxr-xr-x. 1 root root   0 Jan 12 00:00 before_live_cd_exp
> dr-xr-xr-x. 1 root root 178 Dec 14 14:58 root
> dr-xr-xr-x. 1 root root 178 Dec 14 14:58 stable_15_Dec
> drw-------. 1 root root  22 Dec 11 20:05 swap
>
>
> Now to give you the output of the commands and the minor bad news:
>
> 1)   btrfs check --repair /dev/mapper/dm_crypt
>
>     This command actually executed and exited normally, but I could
> see some errors at the end of the command.
>
>     Full output of repair command over here:
>     https://drive.google.com/file/d/17EQ5TYJE5a4iwRGTXXj9Hh38btxFBLAJ/view?usp=sharing
>
> 2)  btrfs check --init-csum-tree /dev/mapper/dm_crypt
>
>    This is where the minor bad news happens.
>
>    This command exited with a "Segmentation Fault(Core Dumped)"
>
>    Full output here:
>    https://drive.google.com/file/d/1IYnLcw-vkZ2UeH0rOZje4kbhzB_tYaKy/view?usp=sharing
>
>    I have my core dumps set to unlimited:
>
>    # ulimit -a
> core file size          (blocks, -c) unlimited
> data seg size           (kbytes, -d) unlimited
> scheduling priority             (-e) 0
> file size               (blocks, -f) unlimited
> pending signals                 (-i) 31030
> max locked memory       (kbytes, -l) 64
> max memory size         (kbytes, -m) unlimited
> open files                      (-n) 1024
> pipe size            (512 bytes, -p) 8
> POSIX message queues     (bytes, -q) 819200
> real-time priority              (-r) 0
> stack size              (kbytes, -s) 8192
> cpu time               (seconds, -t) unlimited
> max user processes              (-u) 31030
> virtual memory          (kbytes, -v) unlimited
> file locks                      (-x) unlimited
>
> But still I was unable to get coredump file as it was not generated:
>
> # coredumpctl list btrfs
> TIME                            PID   UID   GID SIG COREFILE  EXE
> Mon 2021-01-11 22:58:18 IST    4337     0     0  11 none      /usr/sbin/btrfs
>
> Which is weird.
>
> All the outputs are compressed using GZIP, let me know if you are
> unable to download them. The repair command was run before the
> init-csum-tree command.
>
> I have also used your enhanced version of btrfs-progs that you provided:
>
> # dnf repoquery --installed btrfs-progs
> btrfs-progs-0:5.9+git20210108.3783313-0.fc33.1.x86_64
>
> Let me know the next steps ie. Do you need BTRFS logs to diagnose the
> root cause of the problem ?
>
> Thank you once again for your help and perseverance. Couldn't have
> done it without you.

Sorry missed to include the dmesg error for the init-csum-tree command:

[34922.980911] btrfs[4337]: segfault at 60 ip 00005625672ebf81 sp
00007ffee2b38180 error 4 in btrfs[562567287000+96000]
[34922.980939] Code: a0 00 00 00 00 00 00 00 e8 5c a3 ff ff 8b 4c 24
50 4c 89 fe 85 c0 0f 44 44 24 38 45 31 c0 89 44 24 38 48 8b 84 24 a0
00 00 0
0 <8b> 40 60 49 29 87 d0 00 00 00 6a 00 55 4c 8b 9c 24 90 00 00 00 48
[35498.885297] i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

Guess it was caused by some sort of underrun.

-- 
Regards,
Sreyan Chakravarty
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux