On 2017-07-12 12:50, Istvan Gabor wrote:
On Wed, 12 Jul 2017 12:32:30 +0200, Carlos E. R. wrote:
fsck in Leap 42.2:
# fsck -C -t ext3 /dev/md9 fsck from util-linux 2.28 e2fsck 1.42.11 (09-Jul-2014) The filesystem size (according to the superblock) is 7863809 blocks The physical size of the device is 7863791 blocks Either the superblock or the partition table is likely to be corrupt! Abort<y>? no
You do that without looking first at the log to find out what the problem is? :-o
A forced fsck can destroy things.
Thanks. If I know correctly fsck asks for my permission for every single correction if I don't use -p option.
I referred to the last step above: superblock missing --> abort and rethink.
I just wanted to see if there's any file system problem. I looked at the log file suggested but could not interpret it. Here it is right after an unsuccessful mount command:
# mount /dev/md9 /mnt mount: wrong fs type, bad option, bad superblock on /dev/md9, missing codepage or helper program, or other error
In some cases useful info is found in syslog - try dmesg | tail or so.
# dmesg | tail [ 3308.658899] [<ffffffff813295f7>] dump_stack+0x5c/0x85 [ 3308.658910] [<ffffffff8121cf8a>] dput+0x2a/0x250 [ 3308.658921] [<ffffffff8120ff22>] path_put+0x12/0x20 [ 3308.658936] [<ffffffffa0966098>] get_filename_from_opened_fd+0x98/0xd0 [bc_guard] [ 3308.658973] [<ffffffffa09661c3>] wrapper_sys_ftruncate+0x33/0x110 [bc_guard] [ 3308.658988] [<ffffffff8160f772>] entry_SYSCALL_64_fastpath+0x16/0x71 [ 3308.665068] DWARF2 unwinder stuck at entry_SYSCALL_64_fastpath+0x16/0x71
[ 3308.665077] Leftover inexact backtrace:
That's an incomplete kernel crash/oops/whatever. Please post it complete, so that others can investigate/suggest ideas. Don't attempt to do anything on that filesystem yet. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)