Bug 56114 - fsck.minix seems broken on s/390
Summary: fsck.minix seems broken on s/390
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: util-linux
Version: 7.3
Hardware: s390
OS: Linux
medium
low
Target Milestone: ---
Assignee: Elliot Lee
QA Contact: Ben Levenson
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-11-12 21:34 UTC by Ben Levenson
Modified: 2007-04-18 16:38 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2001-11-24 01:28:54 UTC


Attachments (Terms of Use)
fsck.minix strace-interrupted by killing ssh session (after 5+ minutes) (5.02 KB, text/plain)
2001-11-12 21:53 UTC, Ben Levenson
no flags Details

Description Ben Levenson 2001-11-12 21:34:58 UTC
Description of Problem:
fsck.minix hangs on s390.
strace attached.

Version-Release number of selected component (if applicable):
util-linux-2.11f-15
cat /proc/version:
Linux version 2.4.9-9.1 (harald@s390.redhat.de) (gcc version 2.95.3
20010315 (release)) #1 SMP Wed Oct 31 15:33:39 CET 2001


How Reproducible:
100%

Steps to Reproduce:
1. dd if=/dev/zero of=/tmp/minix.img bs=1M count=10
2. mkfs.minix /tmp/minix.img
(3. mount /tmp/minix.img. copy a couple of files. unmount. <-- just did 
 this to verify the functionality of the minix.img, though it is not a
 necessary step to recreate the failure)
4. fsck.minix -lavsmf /tmp/minix.img

Actual Results:
shell hangs...

Expected Results:Forcing filesystem check on /tmp/minix.img.
(these are the results from repeating the steps on i686)
3424 inodes
10240 blocks
Firstdatazone=112 (112)
Zonesize=1024
Maxsize=268966912
Filesystem state=1
namelen=30

     2 0100644   1 /sanity
     3 0100755   1 /sanity_color
     4 0100644   1 /sanity.kdeadmin
     5 0100644   1 /sanity.man-pages
     6 0100644   1 /sanity.mpage

     6 inodes used (0%)
   146 zones used (1%)

     5 regular files
     1 directories
     0 character device files
     0 block device files
     0 links
     0 symbolic links
------
     6 files



Additional Information:
The process can't be interrupted w/ <^-C> or w/ kill -9 <pid>.

Comment 1 Ben Levenson 2001-11-12 21:53:37 UTC
Created attachment 37302 [details]
fsck.minix strace-interrupted by killing ssh session (after 5+ minutes)

Comment 2 Bernhard Rosenkraenzer 2001-11-14 10:39:59 UTC
Since it's hanging in a sync() call, it looks suspiciously like a kernel 
problem. Any ideas, Arjan?


Comment 3 Arjan van de Ven 2001-11-14 10:46:08 UTC
does the same happen with fsck.ext2 ?

Comment 4 Harald Hoyer 2001-11-14 11:26:15 UTC
maybe kupdated died again...


Comment 5 Ben Levenson 2001-11-14 17:25:44 UTC
will try fsck.ext2 once the s/390 is back online.


Comment 6 Ben Levenson 2001-11-14 17:26:43 UTC
didn't mean to change to assigned...
switching back to NEEDINFO


Comment 7 Karsten Hopp 2001-11-14 17:51:16 UTC
removed s/390 minix support in newest util-linux, but fsck.ext2 needs to be 
checked


Comment 8 David Sainty 2001-11-24 01:28:47 UTC
I've never seen a problem w/ fsck.ext2 / e2fsck.


Comment 9 David Sainty 2001-11-30 17:01:24 UTC
Exact steps followed in original report for ext2 - no problems.  Creating and
checking ext[23] fs's has been one of the things tested very regularly. No
problems are known.  Closing.



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