touch-packages team mailing list archive

[DD Park <deedee6905@xxxxxxxxx>]

I am not familiar with the tool, but I was concerned about the
file/directory names. I can look into the -s option
and might be doable. I am still without a working chassis that can handle
as many harddrives I have. I have
a new motherboard and card. I was able to find online other people having
similar problems w/fsck unable to
clean > 16TB. Is that problem considered fixed and in the mainline?  It
will help me prioritize this.

On Fri, Nov 13, 2015 at 10:44 AM, Theodore Ts'o <tytso@xxxxxxx> wrote:

> You do realize that e2image doesn't contain any data blocks --- just
> file system metadata blocks, right?   And if you are concerned about the
> directory names being too revealing, e2image has a -s option which will
> scramble the directory file names.  See the section "RAW IMAGE FILES" in
> the e2image man page.
>
> Failing that, there probably isn't much we can do, short of having you
> get a newer version of e2fsprogs, build it with debugging information
> enabled, and then run it under a debugger so we can get an accurate
> stack trace.   I will note that the stack trace printed by e2fsck
> doesn't look completely sane, since ext2fs_rb_next() doesn't actually
> call any C library functions, and far too many of the stack frames don't
> have symbol names to annotate the addresses.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1345682
>
> Title:
>   fsck on 24TB ext4 keeps crashing
>
> Status in e2fsprogs package in Ubuntu:
>   Incomplete
>
> Bug description:
>   date; fsck -vy /dev/mapper/raid61p1 ;date
>   Thu Jul 17 11:54:21 PDT 2014
>   fsck from util-linux 2.20.1
>   I can't get my ext4 24TB to fsck clean. there came a whole bunch of file
> stat problems after a clean reboot.
>   I tried 3 times so far, and each does something like segfault. I looked
> twice, and the errors were different,
>   but was able to capture one output. The system has 6GB ram, and it used
> up all the memory. ended up adding 25GB
>   of swap as fsck seems to use up a huge amount of memory. After a long
> while, usually after mem use is >90%,
>   I come back to see the fsck has crashed and file system is still not
> clean.
>
>   The reboot was clean and should not  have caused any corruption. the
>   system is using ubuntu-14.04
>
>   # uname -a
>   Linux gigabyte133 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08
> UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
>   root@gigabyte133:~#
>
>   I had to use the 64 bit version since the 32 bit version I couldn't get
> more than 15TB file system built and read
>   that there were compatibility problems between 32bit version with the -O
> 64bit and the 64 bit version so just
>   built the whole thing in 64 bit ubuntu..
>
>
>   e2fsck 1.42.9 (4-Feb-2014)
>
>
>   /dev/mapper/raid61p1 contains a file system with errors, check forced.
>   Pass 1: Checking inodes, blocks, and sizes
>   Inode 203167820 has compression flag set on filesystem without
> compression support.  Clear? yes
>
>   Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil)
>   fsck.ext4[0x4266f1]
>   /lib/x86_64-linux-gnu/libc.so.6(+0x36ff0)[0x7fd38d087ff0]
>   /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_rb_next+0x23)[0x7fd38dc7bc43]
>   /lib/x86_64-linux-gnu/libext2fs.so.2(+0x10670)[0x7fd38dc5e670]
>   fsck.ext4[0x4100f6]# lsb_release -va
>   No LSB modules are available.
>   Distributor ID: Ubuntu
>   Description:    Ubuntu 14.04 LTS
>   Release:        14.04
>   Codename:       trusty
>
>   /lib/x86_64-linux-gnu/libext2fs.so.2(+0x11c3d)[0x7fd38dc5fc3d]
>   /lib/x86_64-linux-gnu/libext2fs.so.2(+0x11f78)[0x7fd38dc5ff78]
>
> /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_block_iterate3+0xa13)[0x7fd38dc60b13]
>   fsck.ext4[0x4115c4]
>   fsck.ext4[0x412699]
>   fsck.ext4[0x412761]
>
> /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_get_next_inode_full+0x59)[0x7fd38dc6c9a9]
>   fsck.ext4(e2fsck_pass1+0x8d8)[0x4130c8]
>   fsck.ext4(e2fsck_run+0x52)[0x40deb2]
>   fsck.ext4(main+0xd27)[0x40a0e7]
>   /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fd38d072ec5]
>   fsck.ext4[0x40bde6]
>   Thu Jul 17 15:55:01 PDT 2014
>
>   # lsb_release -va
>   No LSB modules are available.
>   Distributor ID: Ubuntu
>   Description:    Ubuntu 14.04 LTS
>   Release:        14.04
>   Codename:       trusty
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: util-linux 2.20.1-5.1ubuntu20.1
>   ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
>   Uname: Linux 3.13.0-32-generic x86_64
>   NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
>   ApportVersion: 2.14.1-0ubuntu3.2
>   Architecture: amd64
>   Date: Sat Jul 19 18:49:32 2014
>   InstallationDate: Installed on 2014-07-11 (8 days ago)
>   InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64
> (20140417)
>   ProcEnviron:
>    TERM=xterm
>    PATH=(custom, no user)
>    LANG=en_US.UTF-8
>    SHELL=/bin/bash
>   SourcePackage: util-linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1345682/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1345682

Title:
  fsck on 24TB ext4 keeps crashing

Status in e2fsprogs package in Ubuntu:
  Incomplete

Bug description:
  date; fsck -vy /dev/mapper/raid61p1 ;date
  Thu Jul 17 11:54:21 PDT 2014
  fsck from util-linux 2.20.1
  I can't get my ext4 24TB to fsck clean. there came a whole bunch of file stat problems after a clean reboot.
  I tried 3 times so far, and each does something like segfault. I looked twice, and the errors were different,
  but was able to capture one output. The system has 6GB ram, and it used up all the memory. ended up adding 25GB
  of swap as fsck seems to use up a huge amount of memory. After a long while, usually after mem use is >90%,
  I come back to see the fsck has crashed and file system is still not clean.

  The reboot was clean and should not  have caused any corruption. the
  system is using ubuntu-14.04

  # uname -a
  Linux gigabyte133 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
  root@gigabyte133:~# 

  I had to use the 64 bit version since the 32 bit version I couldn't get more than 15TB file system built and read 
  that there were compatibility problems between 32bit version with the -O 64bit and the 64 bit version so just
  built the whole thing in 64 bit ubuntu..

  
  e2fsck 1.42.9 (4-Feb-2014)

  
  /dev/mapper/raid61p1 contains a file system with errors, check forced.
  Pass 1: Checking inodes, blocks, and sizes
  Inode 203167820 has compression flag set on filesystem without compression support.  Clear? yes

  Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil)
  fsck.ext4[0x4266f1]
  /lib/x86_64-linux-gnu/libc.so.6(+0x36ff0)[0x7fd38d087ff0]
  /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_rb_next+0x23)[0x7fd38dc7bc43]
  /lib/x86_64-linux-gnu/libext2fs.so.2(+0x10670)[0x7fd38dc5e670]
  fsck.ext4[0x4100f6]# lsb_release -va
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu 14.04 LTS
  Release:        14.04
  Codename:       trusty

  /lib/x86_64-linux-gnu/libext2fs.so.2(+0x11c3d)[0x7fd38dc5fc3d]
  /lib/x86_64-linux-gnu/libext2fs.so.2(+0x11f78)[0x7fd38dc5ff78]
  /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_block_iterate3+0xa13)[0x7fd38dc60b13]
  fsck.ext4[0x4115c4]
  fsck.ext4[0x412699]
  fsck.ext4[0x412761]
  /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_get_next_inode_full+0x59)[0x7fd38dc6c9a9]
  fsck.ext4(e2fsck_pass1+0x8d8)[0x4130c8]
  fsck.ext4(e2fsck_run+0x52)[0x40deb2]
  fsck.ext4(main+0xd27)[0x40a0e7]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fd38d072ec5]
  fsck.ext4[0x40bde6]
  Thu Jul 17 15:55:01 PDT 2014

  # lsb_release -va
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu 14.04 LTS
  Release:        14.04
  Codename:       trusty

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: util-linux 2.20.1-5.1ubuntu20.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Sat Jul 19 18:49:32 2014
  InstallationDate: Installed on 2014-07-11 (8 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1345682/+subscriptions