Re: [Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing

2016-03-27 Thread Theodore Ts'o 
On Sun, Mar 27, 2016 at 03:25:40AM -, DD Park wrote:
> Hello, I need your help. This bug seemed to have been placed offline due to
> inactivity. It is still a problem as been working on moving things around
> to get a testing platform. I've been getting new hardware, and started
> another build process to get me to a point of testing. I'm plan on doing a
> little more testing before going into production based on the thought that
> this problem was fixed, but initial testing shows I'm stilll having some
> similar problems. I've built a 18TB file system raid5 ext4, and I was
> crossing my fingers that it would be stable, but I'm seeing all kinds of
> corruptions and doing fsck early I see that the file system doesn't stay
> clean for long. I've built 3 systems so far. Two of them have gone into
> production and I've limited my ext4 to 16TB. I built another system with
> 18TB and  I once I start copying large amounts of files onto the system, I
> start seeing some warning messages indicating some forms of corruption, and
> I stop the copy, run fsck, and I find I do not have a clean file system.
> I'm running ubuntu 14.04.04 LTS on this test system. I've got another near
> identical setup with ubuntu-14.04 and 16TB or less and works fine(this was
> the original system that I saw my corruption. After downsizing, I'm good).
> I've got another with 18TB, but split into a 16TB partition and 2TB
> partition, on a ubuntu-15.04 system and that is working fine. I go back to
> an hybrid system I built to do this test. It is running ubuntu14.04.04 and
> built this one with 18TB. This was an older file server that did not have
> problems that I decomissioned recently so I could do this testing. I
> started my burn in tests and started seeing corruption of the file system.
> As expected the only thing I can determine is that it doesn't seem to like
> >16TB. Please let me know how I can help get this debugged.

So the original problem was about fsck crashing with a seg fault.

That's different from it finding corruptions.  So the first question
is what exactly are you seeing?  Corruptions?   Fsck crashing?   Both?

The next question is are you using resize2fs or not?  There are known
problems with using resize2fs with large partitions, especially if you
aren't using the very latest version of e2fsprogs.  In general on-line
resizing is going to be much safer than off-line resizing (the bugs
were in resize2fs's off-line resizing code).

If you are seeing it crash, the best thing to do is to get the very
latest version of e2fsprogs, and build it, and then run it from there,
so we can get a stack trace with line numbers.  Since I'm about to
release 1.43, ideally you would do this with both 1.42.13 as well as
the tip of the e2fsprogs git's "master" branch.

(Sorry, I don't provide support for distro versions of the kernel and
e2fsprogs.  If you want that, you need to pay $$$ to Canonical and get
their enterprise support product offerring.)

- Ted

P.S.  Also, to be clear, you are are using software raid?

-- 
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:
  Expired

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]

Re: [Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing

2016-03-26 Thread DD Park 
Hello, I need your help. This bug seemed to have been placed offline due to
inactivity. It is still a problem as been working on moving things around
to get a testing platform. I've been getting new hardware, and started
another build process to get me to a point of testing. I'm plan on doing a
little more testing before going into production based on the thought that
this problem was fixed, but initial testing shows I'm stilll having some
similar problems. I've built a 18TB file system raid5 ext4, and I was
crossing my fingers that it would be stable, but I'm seeing all kinds of
corruptions and doing fsck early I see that the file system doesn't stay
clean for long. I've built 3 systems so far. Two of them have gone into
production and I've limited my ext4 to 16TB. I built another system with
18TB and  I once I start copying large amounts of files onto the system, I
start seeing some warning messages indicating some forms of corruption, and
I stop the copy, run fsck, and I find I do not have a clean file system.
I'm running ubuntu 14.04.04 LTS on this test system. I've got another near
identical setup with ubuntu-14.04 and 16TB or less and works fine(this was
the original system that I saw my corruption. After downsizing, I'm good).
I've got another with 18TB, but split into a 16TB partition and 2TB
partition, on a ubuntu-15.04 system and that is working fine. I go back to
an hybrid system I built to do this test. It is running ubuntu14.04.04 and
built this one with 18TB. This was an older file server that did not have
problems that I decomissioned recently so I could do this testing. I
started my burn in tests and started seeing corruption of the file system.
As expected the only thing I can determine is that it doesn't seem to like
>16TB. Please let me know how I can help get this debugged.

On Wed, Nov 18, 2015 at 6:38 PM, Phillip Susi  wrote:

> To jump in for Ted here; I'm pretty sure that "very large" is in the
> millions range.  Whatever the cause though, the best way for us to be
> able to reproduce, diagnose, and fix it is with an image of the
> filesystem, even if it is with the file names scrambled ( the names
> don't really matter anyhow, just the number and possibly placement of
> them ).
>
> --
> 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]
>

Re: [Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing

2016-01-19 Thread DD Park 
Hi. The problem still exists for me, I haven't been able to get equipment
yet, but the data is still sitting on a bunch of hard drives.

On Sun, Jan 17, 2016 at 8:18 PM, Launchpad Bug Tracker <
1345...@bugs.launchpad.net> wrote:

> [Expired for e2fsprogs (Ubuntu) because there has been no activity for
> 60 days.]
>
> ** Changed in: e2fsprogs (Ubuntu)
>Status: Incomplete => Expired
>
> --
> 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:
>   Expired
>
> 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:
  Expired

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

[Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing

2016-01-17 Thread Launchpad Bug Tracker 
[Expired for e2fsprogs (Ubuntu) because there has been no activity for
60 days.]

** Changed in: e2fsprogs (Ubuntu)
   Status: Incomplete => Expired

-- 
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:
  Expired

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing

2015-11-18 Thread Phillip Susi 
To jump in for Ted here; I'm pretty sure that "very large" is in the
millions range.  Whatever the cause though, the best way for us to be
able to reproduce, diagnose, and fix it is with an image of the
filesystem, even if it is with the file names scrambled ( the names
don't really matter anyhow, just the number and possibly placement of
them ).

-- 
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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing

2015-11-17 Thread DD Park 
Hi. I checked into another server that is waiting to upgrade >16TB
pending this issue get resolved.
Can you provide more information as to the statement "very large
number of hard link". This other system has approx 150K hardlinks and
growing daily. I'm not sure if we are talking about millions or
billions or thousands of hardlinks. Is 150K hardlinks considered "very
large" for this problem?

On 11/13/15, craigslist reply  wrote:
> FYI. There was about 15TB (back when I initially ran into the problem,
> maybe about 11-14TB) of hardlinks.
> The Hardlinks are used so that rsync can handle directory name changes and
> not have to copy the whole directory over again. Thus each file would have
> a hardlink. I estimate maybe 40K+ or 80K+ files (I'm not sure if rsync
> counter includes hardlinks or not, but there would have been more than 80K
> files according to rsync) the fsck would use up all available memory. Even
> if I added mega swap space, the program would use it all up. I'm not super
> techie on this, so I can add to my test a temporary removal of all the
> hardlinks after I resolve my own issue of getting a chassis to house all
> the harddrives. I don't expect to have much time to resolve my chassis
> problem within a  month, but now that I know there are some possible
> workarounds, and path moving forward, I can try to raise the priority back
> on this issue. Don't expect quick turn around on my part, but I do need to
> get that file system back operational to get data off the drives so I
> eventually will need to get it to a state where I can do the fsck test.
>
> oh btw, when initially the file system was clean, fsck would work no
> problem as I tested that before using the system. It was after there was
> some file system problems that I later ran fsck and ran into problems. I
> don't know if these people who are successfully running fsck are doing so
> from a non-clean file system.
>
> On Fri, Nov 13, 2015 at 12:09 PM, Theodore Ts'o  wrote:
>
>> There are plenty of people who *are* able to check file systems larger
>> than 16TB.  So talking about it in terms "that problem" doesn't make much
>> sense.
>>
>> There is a known issue where if you are using a huge number of hard links
>> (if you are using a backup solution which uses hard links and a huge
>> number
>> of parallel directory hierarchies) e2fsck uses a large amount of memory.
>> I
>> don't know if that's what you are doing, but if that's what you are
>> doing,
>> it wouldn't surprise me if you are running out of memory.  You should
>> have
>> gotten an explicit "you ran out of memory" error instead of a seg fault,
>> though.
>>
>> There is a way you can use scratch files for some of the data structures
>> that e2fsck needs to track all of the hard links; see the
>> "The [scratch_files] Stanza" section in the e2fsck.conf.  However, this
>> is
>> going to be *SLOW*.The primary use of this was for people who were
>> using 32-bit systems and who didn't have the address space for the memory
>> requirements for large file systems with a large number of hard links.
>>  You may be better off just trying to configure our swap space.  (All of
>> this is assuming the problem is that the file system has a very large
>> number of hard link farms.  Have you confirmed that when you configured
>> 25GB of swap, that the system actually used that amount of swap)?
>>
>> --
>> 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

Re: [Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing

2015-11-13 Thread DD Park 
the nature of the content is confidential so I wouldnt' be able to get you
an e2image of the file system. it has live data. I am guessing that it is
possibly the high number of files or the nature of the file system
corruption.
I know that the fsck was not clean, and it just keeps sucking up memory.

On Wed, Nov 11, 2015 at 5:19 PM, Phillip Susi  wrote:

> I just tried a fresh install of 14.04.2 in a vm with a 20 tb virtual
> disk and fsck seemed to work fine.  It might be specific to your disk
> contents.  If you can reproduce this, please capture an image of the
> filesystem metadata with e2image -r ( and bzip2 that ) and attach it and
> I can try running on that.
>
> --
> 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

[Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing

2015-11-13 Thread Theodore Ts'o 
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 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing

2015-11-13 Thread DD Park 
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  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

[Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing

2015-11-13 Thread Theodore Ts'o 
There are plenty of people who *are* able to check file systems larger than 
16TB.  So talking about it in terms "that problem" doesn't make much sense. 

   

   
There is a known issue where if you are using a huge number of hard links (if 
you are using a backup solution which uses hard links and a huge number of 
parallel directory hierarchies) e2fsck uses a large amount of memory.  I don't 
know if that's what you are doing, but if that's what you are doing, it 
wouldn't surprise me if you are running out of memory.  You should have gotten 
an explicit "you ran out of memory" error instead of a seg fault, though.   
   

   
There is a way you can use scratch files for some of the data structures that 
e2fsck needs to track all of the hard links; see the
   
"The [scratch_files] Stanza" section in the e2fsck.conf.  However, this is 
going to be *SLOW*.The primary use of this was for people who were using 
32-bit systems and who didn't have the address space for the memory 
requirements for large file systems with a large number of hard links.   You 
may be better off just trying to configure our swap space.  (All of this is 
assuming the problem is that the file system has a very large number of hard 
link farms.  Have you confirmed that when you configured 25GB of swap, that the 
system actually used that amount of swap)?

-- 
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:

Re: [Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing

2015-11-13 Thread DD Park 
FYI. There was about 15TB (back when I initially ran into the problem,
maybe about 11-14TB) of hardlinks.
The Hardlinks are used so that rsync can handle directory name changes and
not have to copy the whole directory over again. Thus each file would have
a hardlink. I estimate maybe 40K+ or 80K+ files (I'm not sure if rsync
counter includes hardlinks or not, but there would have been more than 80K
files according to rsync) the fsck would use up all available memory. Even
if I added mega swap space, the program would use it all up. I'm not super
techie on this, so I can add to my test a temporary removal of all the
hardlinks after I resolve my own issue of getting a chassis to house all
the harddrives. I don't expect to have much time to resolve my chassis
problem within a  month, but now that I know there are some possible
workarounds, and path moving forward, I can try to raise the priority back
on this issue. Don't expect quick turn around on my part, but I do need to
get that file system back operational to get data off the drives so I
eventually will need to get it to a state where I can do the fsck test.

oh btw, when initially the file system was clean, fsck would work no
problem as I tested that before using the system. It was after there was
some file system problems that I later ran fsck and ran into problems. I
don't know if these people who are successfully running fsck are doing so
from a non-clean file system.

On Fri, Nov 13, 2015 at 12:09 PM, Theodore Ts'o  wrote:

> There are plenty of people who *are* able to check file systems larger
> than 16TB.  So talking about it in terms "that problem" doesn't make much
> sense.
>
> There is a known issue where if you are using a huge number of hard links
> (if you are using a backup solution which uses hard links and a huge number
> of parallel directory hierarchies) e2fsck uses a large amount of memory.  I
> don't know if that's what you are doing, but if that's what you are doing,
> it wouldn't surprise me if you are running out of memory.  You should have
> gotten an explicit "you ran out of memory" error instead of a seg fault,
> though.
>
> There is a way you can use scratch files for some of the data structures
> that e2fsck needs to track all of the hard links; see the
> "The [scratch_files] Stanza" section in the e2fsck.conf.  However, this is
> going to be *SLOW*.The primary use of this was for people who were
> using 32-bit systems and who didn't have the address space for the memory
> requirements for large file systems with a large number of hard links.
>  You may be better off just trying to configure our swap space.  (All of
> this is assuming the problem is that the file system has a very large
> number of hard link farms.  Have you confirmed that when you configured
> 25GB of swap, that the system actually used that amount of swap)?
>
> --
> 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:

Re: [Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing

2015-11-11 Thread DD Park 
As of 1 month ago I was still having the problem. The chassis last month
has failed and i don't have another chassis that can handle that many
drives. I am on hold until I can get funding to get another chassis. I have
moved to 6TB drives for another setup, but I limited the partition to 16TB
since the fsck doesn't work on larger file systems. I am waiting for the
fsck problem to get fixed before creating another >16TB file system.

On Tue, Nov 10, 2015 at 5:42 PM, Phillip Susi  wrote:

> Are you still able to reproduce this?
>
> ** Package changed: util-linux (Ubuntu) => e2fsprogs (Ubuntu)
>
> ** Changed in: e2fsprogs (Ubuntu)
>Status: New => Incomplete
>
> --
> 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.

[Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing

2015-11-11 Thread Phillip Susi 
I just tried a fresh install of 14.04.2 in a vm with a 20 tb virtual
disk and fsck seemed to work fine.  It might be specific to your disk
contents.  If you can reproduce this, please capture an image of the
filesystem metadata with e2image -r ( and bzip2 that ) and attach it and
I can try running on that.

-- 
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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing

2015-11-10 Thread Phillip Susi 
Are you still able to reproduce this?

** Package changed: util-linux (Ubuntu) => e2fsprogs (Ubuntu)

** Changed in: e2fsprogs (Ubuntu)
   Status: New => Incomplete

-- 
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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp