Your message dated Tue, 31 Dec 2013 14:37:09 -0500
with message-id <[email protected]>
and subject line Re: e2fsprogs: Seems to be hanging and then is suddenly 
finished...
has caused the Debian Bug report #730225,
regarding e2fsprogs: Seems to be hanging and then is suddenly finished...
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
730225: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730225
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: e2fsprogs
Version: 1.42.8-1
Severity: normal

Dear Maintainer,

I don't know whether you can do something with this report, but I'll
file it anyway.

Today I had an fsck on my main (ext3) partition. It's a rather large
partition (500GB), so it takes a while. It progressed slowly (with
irregular speeds), but at 33.9% it stayed for about 15 minutes after
having done about 10-15 minutes on the first 33.9%. Then I looked away
for a few minutes and I saw my login-screen. So it had suddenly
finished.

I was very close to pressing the reset button of my PC, as it really
looked like it was stuck.

It's almost as if the progress indicator just hung and in the mean time
the fsck just continued normally. Very confusing and upsetting!

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages e2fsprogs depends on:
ii  e2fslibs    1.42.8-1
ii  libblkid1   2.20.1-5.5
ii  libc6       2.17-93
ii  libcomerr2  1.42.8-1
ii  libss2      1.42.8-1
ii  libuuid1    2.20.1-5.5
ii  util-linux  2.20.1-5.5

e2fsprogs recommends no packages.

Versions of packages e2fsprogs suggests:
pn  e2fsck-static  <none>
ii  gpart          0.1h-11+b1
ii  parted         2.3-16

-- no debconf information

--- End Message ---
--- Begin Message ---
Oops, I typo'ed the bug number, sorry.

                                - Ted

On Tue, Dec 31, 2013 at 01:30:13AM -0500, Theodore Ts'o wrote:
> On Fri, Nov 22, 2013 at 09:40:26PM +0100, Manuel Bilderbeek wrote:
> > I don't know whether you can do something with this report, but I'll
> > file it anyway.
> > 
> > Today I had an fsck on my main (ext3) partition. It's a rather large
> > partition (500GB), so it takes a while. It progressed slowly (with
> > irregular speeds), but at 33.9% it stayed for about 15 minutes after
> > having done about 10-15 minutes on the first 33.9%. Then I looked away
> > for a few minutes and I saw my login-screen. So it had suddenly
> > finished.
> 
> At 33.9 percent it would have been checking inodes in the inode table.
> Assuming you are using the textual completion bar (as opposeed to some
> fancy-shamcy graphical completion bar, which I don't think Debian
> supports), there's really nothing that can go wrong.  At one point, I
> believe Ubuntu had some scheme where it was getting the completion
> information and displaying it on the graphical init screen.  If that
> is hanging for some reason, that would be a bug in the fancy graphical
> boot up display system, and it's not a bug in e2fsprogs.  You'll need
> to figure out what graphical boot up system you are using, and file
> your bug against that.
> 
> If you are seeing a textual completion bar, i.e, something which
> looked like this:
> 
> /dev/lambda/backup: |==============                                  - 28.4%  
>  
> 
> Then the only explanation I can think of is either a very badly
> corrupted file system (but then you would have seen lots of error
> messages scrolling buy), or some kind of hardware fault.
> 
> In any case, there really isn't anything I can do about this, so I'm
> closing the bug report.
> 
> Regards,
> 
>                                       - Ted

--- End Message ---

Reply via email to