public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jurgen Schulz <jmschulz@earthlink.net>
To: xfs@oss.sgi.com
Subject: system freeze with xfs
Date: Tue, 24 Apr 2007 09:50:57 -0700	[thread overview]
Message-ID: <1177433458.3360.12.camel@localhost.localdomain> (raw)

When I create an xfs filesystem and run
'stress' (http://weather.ou.edu/~apw/projects/stress/stress.html) I can
induce a system freeze (hang, no panic). There are no issues if I create
a jfs filesystem (on the same disk) or run 'stress' on a different disk
(ext3)

I'd like to know how I could go about debugging this, otherwise I will
have to switch filesystem types.


Details:
% stress -d 2 --hdd-noclean --hdd-bytes 3G --verbose

Fedora Core 5 
2.6.20-1.2312.fc5 #1 Tue Apr 10 15:09:44 EDT 2007 i686 athlon i386
GNU/Linux

# /sbin/mkfs.xfs -f  /dev/VolTest/test 
meta-data=/dev/VolTest/test      isize=256    agcount=16, agsize=198656
blks
         =                       sectsz=512  
data     =                       bsize=4096   blocks=3178496, imaxpct=25
         =                       sunit=0      swidth=0 blks, unwritten=1
naming   =version 2              bsize=4096  
log      =internal log           bsize=4096   blocks=2560, version=1
         =                       sectsz=512   sunit=0 blks
realtime =none                   extsz=65536  blocks=0, rtextents=0

# /sbin/hdparm /dev/hdk 

/dev/hdk:
 multcount    = 16 (on)
 IO_support   =  0 (default 16-bit)
 unmaskirq    =  0 (off)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    = 256 (on)
 geometry     = 25228/16/63, sectors = 25429824, start = 0

             reply	other threads:[~2007-04-24 17:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-24 16:50 Jurgen Schulz [this message]
2007-04-24 17:29 ` system freeze with xfs Eric Sandeen
2007-04-24 22:55 ` Chris Wedgwood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1177433458.3360.12.camel@localhost.localdomain \
    --to=jmschulz@earthlink.net \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox