Bug 34190 - parallel fsck overly aggressive on newer devices
parallel fsck overly aggressive on newer devices
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: e2fsprogs (Show other bugs)
7.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Florian La Roche
Aaron Brown
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-03-30 23:10 EST by Jason Duerstock
Modified: 2007-04-18 12:32 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-04-01 11:57:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
patch to fix bug (1.26 KB, patch)
2001-03-30 23:13 EST, Jason Duerstock
no flags Details | Diff

  None (edit)
Description Jason Duerstock 2001-03-30 23:10:45 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; MSNIA; Windows 98)


on /dev/hd[efgh]* and /dev/sd[h-z]*, fsck will try to parallel check 
multiple partitions on the same spindle

Reproducible: Always
Steps to Reproduce:
1. make multiple partitions on /dev/hde
2. shutdown system uncleanly
3. watch fsck drag
	

Actual Results:  see #3

Expected Results:  each partition should be checked individually

patch can be found at http://justin.net/~jason/fsck.patch
Comment 1 Jason Duerstock 2001-03-30 23:13:22 EST
Created attachment 14326 [details]
patch to fix bug
Comment 2 Jason Duerstock 2001-04-01 11:56:56 EDT
Ummm...it seems I stupidly submitted a non-working patch, before testing it.  
Please disregard it. :(

Comment 3 Florian La Roche 2001-04-06 16:59:28 EDT
e2fsprogs 1.19-4 and high should have a larger set of names. Can you please
check if
http://people.redhat.com/laroche/e2fsprogs-1.19-4.src.rpm fixes your problems?

Thanks for this report.
Comment 4 Jason Duerstock 2001-04-07 22:49:34 EDT
The file in this URL does not exist.

Note You need to log in before you can comment on or make changes to this bug.