xfs
[Top] [All Lists]

ADD 801063 - mkfs.xfs after having ext2 mounted on a device can fail

To: nathans@xxxxxxxxxxxx
Subject: ADD 801063 - mkfs.xfs after having ext2 mounted on a device can fail
From: pv@xxxxxxxxxxxxx (lord@xxxxxxx)
Date: Thu, 7 Sep 2000 08:48:38 -0700 (PDT)
Cc: linux-xfs@xxxxxxxxxxx
Reply-to: sgi.bugs.xfs@xxxxxxxxxxxxxxxxx
Sender: owner-linux-xfs@xxxxxxxxxxx
Webexec: webpvupdate,pvincident
Webpv: jen.americas.sgi.com
View Incident: 
http://co-op.engr.sgi.com/BugWorks/code/bwxquery.cgi?search=Search&wlong=1&view_type=Bug&wi=801063

 Status : open                         Priority : 3                         
 Assigned Engineer : nathans           Submitter : lord                     
*Modified User : lord                 *Modified User Domain : sgi.com       
*Description :
Running mkfs to build an xfs filesystem after a partition has
been mounted as ext2 has periodically failed for me. The failure
is usually this:

[root@lord /]# mkfs -t xfs -f -l size=16000b /dev/sda4
meta-data=/dev/sda4              isize=256    agcount=8, agsize=149104 blks
data     =                       bsize=4096   blocks=1192826, imaxpct=25
         =                       sunit=0      swidth=0 blks, unwritten=0
naming   =version 2              bsize=4096  
log      =internal log           bsize=4096   blocks=16000

.....


==========================
ADDITIONAL INFORMATION (ADD)
From: lord@xxxxxxx (BugWorks)
Date: Sep 07 2000 08:48:37AM
==========================

A couple more data points:

 o I was running a debug version of mkfs, it does not dump
   core, just exists.

 o running ltrace crashed the system in a copy_from_user writing
   to the block device.

This may have more to do with the state ext2 leaves the block
device than anything else. I seem to recall that they deliberately
do not purge cached data on unmount (flush yes, thow away no).

Not sure what this might have to do with it though.

This does appear to be repeatable on my box though.

<Prev in Thread] Current Thread [Next in Thread>