[opensuse-factory] scary fsck output
13.2/3.16.7 # e2fsck /dev/sdb2 e2fsck 1.42.12 (29-Aug-2014) ST32000542ASp1: clean, 334/61054976 files, 210156348/244189440 blocks Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil) e2fsck[0x427fd1] /lib64/libc.so.6(+0x35200)[0x7f0ef74cc200] /lib64/libext2fs.so.2(ext2fs_free_dblist+0xd)[0x7f0ef80ac6fd] e2fsck(e2fsck_reset_context+0xf8)[0x40e9e8] e2fsck(e2fsck_free_context+0x16)[0x40ec66] e2fsck(main+0x2600)[0x40c870] /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f0ef74b8b05] e2fsck[0x40cc8f] TW/3.18.1 # e2fsck /dev/sdb2 e2fsck 1.42.12 (29-Aug-2014) e2fsck: need terminal for interactive repairs Same system, same disk, 13.1 behaves in tradition, all OK. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 07/01/15 a las 07:08, Felix Miata escribió:
13.2/3.16.7 # e2fsck /dev/sdb2 e2fsck 1.42.12 (29-Aug-2014) ST32000542ASp1: clean, 334/61054976 files, 210156348/244189440 blocks Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil)
Hrmmmm.. "SI_KERNEL Sent by the kernel." it is undocumented. open a bug report so kernel folks can find what's going on. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 2015-01-07 13:59, Cristian Rodríguez wrote:
El 07/01/15 a las 07:08, Felix Miata escribió:
13.2/3.16.7 # e2fsck /dev/sdb2 e2fsck 1.42.12 (29-Aug-2014) ST32000542ASp1: clean, 334/61054976 files, 210156348/244189440 blocks Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil)
Hrmmmm.. "SI_KERNEL Sent by the kernel." it is undocumented. open a bug report so kernel folks can find what's going on.
It is documented (well, at least mentioned) in sigaction(3). Userspace attempts to dereference a pointer. It is of course the kernel which will try to satisfy that paging request, but cannot, as this is apparently a NULL pointer and there is no page mapped at 0x0 for e2fsck. Thus SIGSEGV is raised, naturally by the kernel, so the SI_KERNEL origin is well-formed. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Jan Engelhardt composed on 2015-01-07 14:11 (UTC+0100):
Cristian RodrÃguez wrote:
Felix Miata composed:
13.2/3.16.7 # e2fsck /dev/sdb2 e2fsck 1.42.12 (29-Aug-2014) ST32000542ASp1: clean, 334/61054976 files, 210156348/244189440 blocks Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil)
Hrmmmm.. "SI_KERNEL Sent by the kernel." it is undocumented. open a bug report so kernel folks can find what's going on.
It is documented (well, at least mentioned) in sigaction(3).
Userspace attempts to dereference a pointer. It is of course the kernel which will try to satisfy that paging request, but cannot, as this is apparently a NULL pointer and there is no page mapped at 0x0 for e2fsck. Thus SIGSEGV is raised, naturally by the kernel, so the SI_KERNEL origin is well-formed.
Does this mean a bug report is not indicated? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday 2015-01-08 11:03, Felix Miata wrote:
# e2fsck /dev/sdb2 e2fsck 1.42.12 (29-Aug-2014) ST32000542ASp1: clean, 334/61054976 files, 210156348/244189440 blocks Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil)
Hrmmmm.. "SI_KERNEL Sent by the kernel." it is undocumented. open a bug report so kernel folks can find what's going on.
It is documented (well, at least mentioned) in sigaction(3).
Userspace attempts to dereference a pointer. It is of course the kernel which will try to satisfy that paging request, but cannot, as this is apparently a NULL pointer and there is no page mapped at 0x0 for e2fsck. Thus SIGSEGV is raised, naturally by the kernel, so the SI_KERNEL origin is well-formed.
Does this mean a bug report is not indicated?
SIGSEGV does not indicate a bug report, it indicates a bug! :) One that maybe should be reported. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/08/2015, 11:19 AM, Jan Engelhardt wrote:
On Thursday 2015-01-08 11:03, Felix Miata wrote:
# e2fsck /dev/sdb2 e2fsck 1.42.12 (29-Aug-2014) ST32000542ASp1: clean, 334/61054976 files, 210156348/244189440 blocks Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil)
Hrmmmm.. "SI_KERNEL Sent by the kernel." it is undocumented. open a bug report so kernel folks can find what's going on.
It is documented (well, at least mentioned) in sigaction(3).
Userspace attempts to dereference a pointer. It is of course the kernel which will try to satisfy that paging request, but cannot, as this is apparently a NULL pointer and there is no page mapped at 0x0 for e2fsck. Thus SIGSEGV is raised, naturally by the kernel, so the SI_KERNEL origin is well-formed.
Does this mean a bug report is not indicated?
SIGSEGV does not indicate a bug report, it indicates a bug! :) One that maybe should be reported.
And look into the output of dmesg after running, there should be a line with more info. It would be also helpful to install e2fsprogs-debuginfo and run e2fsck from gdb: $ gdb --args e2fsck /dev/sdb2 (gdb) r <crash> (gdb) where <stacktrace> regards, -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Jiri Slaby composed on 2015-01-08 11:29 (UTC+0100):
Jan Engelhardt wrote:
Felix Miata wrote:
# e2fsck /dev/sdb2 e2fsck 1.42.12 (29-Aug-2014) ST32000542ASp1: clean, 334/61054976 files, 210156348/244189440 blocks Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil)
Hrmmmm.. "SI_KERNEL Sent by the kernel." it is undocumented. open a bug report so kernel folks can find what's going on.
It is documented (well, at least mentioned) in sigaction(3).
Userspace attempts to dereference a pointer. It is of course the kernel which will try to satisfy that paging request, but cannot, as this is apparently a NULL pointer and there is no page mapped at 0x0 for e2fsck. Thus SIGSEGV is raised, naturally by the kernel, so the SI_KERNEL origin is well-formed.
Does this mean a bug report is not indicated?
SIGSEGV does not indicate a bug report, it indicates a bug! :) One that maybe should be reported.
And look into the output of dmesg after running, there should be a line with more info. It would be also helpful to install e2fsprogs-debuginfo and run e2fsck from gdb: $ gdb --args e2fsck /dev/sdb2 (gdb) r <crash> (gdb) where <stacktrace>
http://bugzilla.opensuse.org/show_bug.cgi?id=912229 I was unable to locate any e2fsprogs.debuginfo package for TW. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Felix Miata
Jiri Slaby composed on 2015-01-08 11:29 (UTC+0100):
Jan Engelhardt wrote:
Felix Miata wrote:
> # e2fsck /dev/sdb2 > e2fsck 1.42.12 (29-Aug-2014) > ST32000542ASp1: clean, 334/61054976 files, 210156348/244189440 blocks > Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil)
Hrmmmm.. "SI_KERNEL Sent by the kernel." it is undocumented. open a bug report so kernel folks can find what's going on.
It is documented (well, at least mentioned) in sigaction(3).
Userspace attempts to dereference a pointer. It is of course the kernel which will try to satisfy that paging request, but cannot, as this is apparently a NULL pointer and there is no page mapped at 0x0 for e2fsck. Thus SIGSEGV is raised, naturally by the kernel, so the SI_KERNEL origin is well-formed.
Does this mean a bug report is not indicated?
SIGSEGV does not indicate a bug report, it indicates a bug! :) One that maybe should be reported.
And look into the output of dmesg after running, there should be a line with more info. It would be also helpful to install e2fsprogs-debuginfo and run e2fsck from gdb: $ gdb --args e2fsck /dev/sdb2 (gdb) r <crash> (gdb) where <stacktrace>
http://bugzilla.opensuse.org/show_bug.cgi?id=912229
I was unable to locate any e2fsprogs.debuginfo package for TW.
http://software.opensuse.org/package/e2fsprogs click on the icon click on "show other versions" select Tumbleweed select "show unstable packages" chouse yer poizen or: zypper ref; zypper se -s e2fsprogs -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Patrick Shanahan composed on 2015-01-08 14:15 (UTC-0500):
* Felix Miata composed:
I was unable to locate any e2fsprogs.debuginfo package for TW.
I miswrote. What I should have written was zypper se -s was unable...
click on the icon click on "show other versions" select Tumbleweed select "show unstable packages"
I did that prior to OP. However, I did that here, on 11.4, where 1-click is not an option for installing anything elsewhere on the LAN. As always, software.opensuse.org fails to offer up sufficient info to be successful in getting any of its listed results installed at a shell prompt. I clicked the official release 64 bit link http://download.opensuse.org/factory/repo/oss/suse/x86_64/e2fsprogs-debuginf... anyway. It produced a 404 page. Same result on 32 bit link.
chouse yer poizen
or: zypper ref; zypper se -s e2fsprogs
That, after adding the debug repo, is exactly what failed and fails to produce a useful result. Per arch, there are only e2fsprogs and e2fsprogs-devel among the results. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, 8 Jan 2015 21:06, Felix Miata
Patrick Shanahan composed on 2015-01-08 14:15 (UTC-0500):
* Felix Miata composed:
I was unable to locate any e2fsprogs.debuginfo package for TW.
I miswrote. What I should have written was
zypper se -s was unable...
click on the icon click on "show other versions" select Tumbleweed select "show unstable packages"
I did that prior to OP. However, I did that here, on 11.4, where 1-click is not an option for installing anything elsewhere on the LAN. As always, software.opensuse.org fails to offer up sufficient info to be successful in getting any of its listed results installed at a shell prompt.
I clicked the official release 64 bit link http://download.opensuse.org/factory/repo/oss/suse/x86_64/e2fsprogs-debuginf... anyway. It produced a 404 page. Same result on 32 bit link.
chouse yer poizen
or: zypper ref; zypper se -s e2fsprogs
That, after adding the debug repo, is exactly what failed and fails to produce a useful result. Per arch, there are only e2fsprogs and e2fsprogs-devel among the results.
AFAIK there is a problem with generating the *-debuginfo rpms for Factory and Tumbleweed ATM. Some error in OBS I believe. In an other thread here on the ml there was a discussion about that. So, anyone that mentions installing *-debuginfo rpms atm has to prove their real, download-able existence, or does his very best to prove his ignorance in public. - Yamaban. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/07/2015 05:08 AM, Felix Miata wrote:
13.2/3.16.7 # e2fsck /dev/sdb2 e2fsck 1.42.12 (29-Aug-2014) ST32000542ASp1: clean, 334/61054976 files, 210156348/244189440 blocks Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil) e2fsck[0x427fd1] /lib64/libc.so.6(+0x35200)[0x7f0ef74cc200] /lib64/libext2fs.so.2(ext2fs_free_dblist+0xd)[0x7f0ef80ac6fd] e2fsck(e2fsck_reset_context+0xf8)[0x40e9e8] e2fsck(e2fsck_free_context+0x16)[0x40ec66] e2fsck(main+0x2600)[0x40c870] /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f0ef74b8b05] e2fsck[0x40cc8f]
TW/3.18.1 # e2fsck /dev/sdb2 e2fsck 1.42.12 (29-Aug-2014) e2fsck: need terminal for interactive repairs
Same system, same disk, 13.1 behaves in tradition, all OK.
It appears your disk is all fscked up. ;-) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (7)
-
Cristian Rodríguez -
Felix Miata -
James Knott -
Jan Engelhardt -
Jiri Slaby -
Patrick Shanahan -
Yamaban