Re: fsck crashes on buster
daggs wrote: > can you point me to the bugzilla where I can open the bug? No bugzilla just by command line tool: reportbug. Can be installed by package: reportbug. https://www.debian.org/Bugs/Reporting Best regards, Klaus. -- Klaus Singvogel GnuPG-Key-ID: 1024R/5068792D 1994-06-27
Re: fsck crashes on buster
Greetings Michael, > Sent: Wednesday, July 08, 2020 at 4:12 PM > From: "Michael Stone" > To: "daggs" > Cc: debian-user@lists.debian.org > Subject: Re: fsck crashes on buster > > On Wed, Jul 08, 2020 at 10:17:44AM +0200, daggs wrote: > >my backup hdd has errors in the fs, so I've stopped the backup process and > >unmounted it. > >when I run fsck /dev/sdc1, I get this: > >root@utilsserver:/home/igor# fsck /dev/sdc1 > >fsck from util-linux 2.33.1 > >e2fsck 1.44.5 (15-Dec-2018) > >backup contains a file system with errors, check forced. > >Pass 1: Checking inodes, blocks, and sizes > >Pass 2: Checking directory structure > >Signal (11) SIGSEGV si_code=SEGV_MAPERR fault addr=0x13 > > You'll have much better luck filing a bug than contacting debian-user. > (The maintainer is very responsive, but doesn't AFAIK read debian-user.) > > can you point me to the bugzilla where I can open the bug?
Re: fsck crashes on buster
On Wed, Jul 08, 2020 at 10:17:44AM +0200, daggs wrote: my backup hdd has errors in the fs, so I've stopped the backup process and unmounted it. when I run fsck /dev/sdc1, I get this: root@utilsserver:/home/igor# fsck /dev/sdc1 fsck from util-linux 2.33.1 e2fsck 1.44.5 (15-Dec-2018) backup contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Signal (11) SIGSEGV si_code=SEGV_MAPERR fault addr=0x13 You'll have much better luck filing a bug than contacting debian-user. (The maintainer is very responsive, but doesn't AFAIK read debian-user.)
fsck crashes on buster
Greetings, my backup hdd has errors in the fs, so I've stopped the backup process and unmounted it. when I run fsck /dev/sdc1, I get this: root@utilsserver:/home/igor# fsck /dev/sdc1 fsck from util-linux 2.33.1 e2fsck 1.44.5 (15-Dec-2018) backup contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Signal (11) SIGSEGV si_code=SEGV_MAPERR fault addr=0x13 fsck.ext3(+0x31a59)[0x55bc7d8afa59] /lib/x86_64-linux-gnu/libc.so.6(+0x37840)[0x7feed55ab840] /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_rb_next+0x23)[0x7feed57e8b33] /lib/x86_64-linux-gnu/libext2fs.so.2(+0x17802)[0x7feed57c1802] /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_icount_increment+0x158)[0x7feed57d3d48] fsck.ext3(+0x21645)[0x55bc7d89f645] fsck.ext3(+0x22997)[0x55bc7d8a0997] /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_dblist_iterate3+0x5f)[0x7feed57c72bf] fsck.ext3(e2fsck_pass2+0x18a)[0x55bc7d89d9ba] fsck.ext3(e2fsck_run+0x5a)[0x55bc7d89166a] fsck.ext3(main+0xcce)[0x55bc7d88d2be] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7feed559809b] fsck.ext3(_start+0x2a)[0x55bc7d88f58a] the os is updated to latest. any hints on how to fix it? I'd rather not turn it off to extract the hdd as it is a production server. Thanks, Dagg.