How long does it take to fsck an 80GB hard drive?

Posted by: tanstaafl.

How long does it take to fsck an 80GB hard drive? - 02/12/2005 21:57

How long does it take to fsck an 80GB hard drive?

I am in the middle of manually fsck-ing my dual 80GB MK-IIA, and need to know if it is going to be done before I get off work.

Anyone?

tanstaafl.
Posted by: wfaulk

Re: How long does it take to fsck an 80GB hard drive? - 02/12/2005 22:02

Moved from Off Topic. Because it's not.
Posted by: tanstaafl.

Re: How long does it take to fsck an 80GB hard drive? - 02/12/2005 23:09

How long does it take to fsck an 80GB hard drive?


Apparently there is no firm answer to this. It probably depends on how many files you have on each drive.

The first drive took about an hour to fsck. The second one took 20 minutes.

tanstaafl.
Posted by: jimhogan

Re: How long does it take to fsck an 80GB hard drive? - 03/12/2005 00:28

Quote:
The first drive took about an hour to fsck. The second one took 20 minutes.

It is entirely dependent on how fsck'd up your drives are.
Posted by: pgrzelak

Re: How long does it take to fsck an 80GB hard drive? - 03/12/2005 14:27

Well, it certainly depends on how full they are. A full 80GB drive can take up to about an hour (from memory). This is improved if the drive is not completely full, if you have more memory / swap enabled and if there are no errors.
Posted by: Mataglap

Re: How long does it take to fsck an 80GB hard drive? - 04/12/2005 22:08

Too long, unless you formatted with the spare superblock according to Roger's site.

I think it's between 10 and 20 minutes.

Also, since you've a dual drive, you should be able to run the fsck on each drive in parallel. Make sure fsck pass numbers are set up in /etc/fstab ( / = 1, and everything else = 2) and add a "-A" to your fsck, "fsck -faAy" fsck is smart enough to not check multiple partitions on the same drive simultaneously.

--Nathan
Posted by: tman

Re: How long does it take to fsck an 80GB hard drive? - 04/12/2005 22:29

Quote:
I think it's between 10 and 20 minutes.

Huh? My 3/4 full 60GB takes longer than that and I know it is good.
Posted by: Mataglap

Re: How long does it take to fsck an 80GB hard drive? - 05/12/2005 00:20

Quote:
Quote:
I think it's between 10 and 20 minutes.

Huh? My 3/4 full 60GB takes longer than that and I know it is good.

Code:

mataglap:/empeg/bin# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 15M 11M 4.4M 72% /
/dev/hda2 34M 19M 13M 59% /programs0
/dev/hdc2 15M 11M 4.4M 72% /programs1
/dev/hda4 74G 58G 16G 78% /drive0
/dev/hdc4 15M 11M 4.4M 72% /drive1
/dev/hdc5 15M 11M 4.4M 72% /root1
mataglap:/empeg/bin# ro
mataglap:/empeg/bin# rom
mataglap:/empeg/bin# umount /drive0
mataglap:/empeg/bin# cat /proc/mounts
/dev/root / ext2 ro 0 0
/dev/hda2 /programs0 ext2 ro 0 0
none /proc proc rw 0 0
mataglap:/empeg/bin# time fsck -fay /dev/hda4
Parallelizing fsck version 1.19 (13-Jul-2000)
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/hda4: 43863/610304 files (2.4% non-contiguous), 15265873/19510942 blocks

real 5m30.844s
user 0m40.230s
sys 0m30.470s
mataglap:/empeg/bin#



Don't know what to say. Did you format with the sparse superblock?

--Nathan
Posted by: wfaulk

Re: How long does it take to fsck an 80GB hard drive? - 05/12/2005 14:21

Yeah, but your filesystem was unmounted cleanly. I don't know about Doug's or what situation Trevor was referring to.
Posted by: tanstaafl.

Re: How long does it take to fsck an 80GB hard drive? - 05/12/2005 20:58

I don't know about Doug's or what situation Trevor was referring to.

My situation was caused by an emplode failure during re-synch (lost network connection) so it got corrupted while it was in RW mode.

The manual fsck (on each drive) and manual database rebuild fixed everything. SInce the first drive took about an hour, and the second one only 20 minutes, I suspect that both Bitt and Jim (Hogan) are correct -- the first disk is the primary and is nearly full; the second was added later and is perhaps 25% full. (just guessing -- since the first one was nearly full when I added the second, and I haven't deleted anything) Probably the corruption was on the first disk.

tanstaafl.