fsck taking way too long 20 hours & still going

Bug #1567567 reported by DD Park
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
e2fsprogs (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hi, I have a 24T file system ext4, ran fsck. It is running fsck for 20 hours so far and looks like it will keep on going.
The system is not a slow machine at all, relatively new server.
I checked top and saw that CPU usage was not high. I seen similar problem like this before but CPU usage
was high in the past.

I'm using ubuntu-14.04.4 lts. and running this on the 2nd extra copy of the superblock. I didn't want to
do it with the main copy. I ran e2image -r -s on the main superblock but it wouldn't create an image file.

I doubt that anything useful is happening and I don't know how to debug this further so please advise
if I should keep it going else I'm likely to shut it down soon

Revision history for this message
Theodore Ts'o (tytso) wrote :

Has fsck run spit out any errors or output? If you have a completion output, has it given an percentage output, or some other way of determining how far along fsck is going?

When e2image wouldn't create an image file, did it report any errors?

Revision history for this message
DD Park (deedee6905) wrote : Re: [Bug 1567567] Re: fsck taking way too long 20 hours & still going

No erros, I do see hd lights going on, I do see on Top program that the
CPU% changes and fluctuates so I guess something is going on. I saw some
messages with the superblock (when ran e2image - i sent those to you in
different email). so I wanted to try with a different superblock (not to
familiar with this process, but gave it a go). I suspect that this is
related to >16TB and I guess this problem won't happen <16TB. I've never
seen this problem on any of my other <16T servers.

On Thu, Apr 7, 2016 at 11:26 AM, Theodore Ts'o <email address hidden> wrote:

> Has fsck run spit out any errors or output? If you have a completion
> output, has it given an percentage output, or some other way of
> determining how far along fsck is going?
>
> When e2image wouldn't create an image file, did it report any errors?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1567567
>
> Title:
> fsck taking way too long 20 hours & still going
>
> Status in e2fsprogs package in Ubuntu:
> New
>
> Bug description:
> Hi, I have a 24T file system ext4, ran fsck. It is running fsck for 20
> hours so far and looks like it will keep on going.
> The system is not a slow machine at all, relatively new server.
> I checked top and saw that CPU usage was not high. I seen similar
> problem like this before but CPU usage
> was high in the past.
>
> I'm using ubuntu-14.04.4 lts. and running this on the 2nd extra copy of
> the superblock. I didn't want to
> do it with the main copy. I ran e2image -r -s on the main superblock
> but it wouldn't create an image file.
>
> I doubt that anything useful is happening and I don't know how to debug
> this further so please advise
> if I should keep it going else I'm likely to shut it down soon
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1567567/+subscriptions
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.