From: Stanislaw Gruszka <stf_xl@wp.pl>
To: David Chinner <dgc@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: BUG: xfs on linux lvm - lvconvert random hungs when doing i/o
Date: Wed, 26 Mar 2008 15:02:19 +0100 [thread overview]
Message-ID: <200803261502.19930.stf_xl@wp.pl> (raw)
In-Reply-To: <20080325020223.GB108924158@sgi.com>
On Tuesday 25 March 2008, David Chinner wrote:
> That points to I/O not completing (not an XFS problem at all), or
> the filesystem freeze is just taking a long time to run (as it has
> to sync everything to disk). Given that this is a snapshot target,
> writing new blocks will take quite some time. Is the system still
> making writeback progress when in this state, or is it really hung?
That is real deadlock, operations which normally takes few minutes,
hangs for few hours until I restart machine.
This bug is very strange because I can't catch it with more verbose
debug and tracing options,
I did more tests without debugging options and looks that version from
sgi cvs (2.6.25-rc3) works well. I did also test with two patches you suggest,
applied (with some troubles) for 2.6.24.2, but finally things hung after
2 days - better than without patches, as you expected.
So, looks things are fixed in sgi cvs repository. Don't know if these are
xfs or other subsystem (device-mapper?) fixes, anyway I can't reproduce
bug on this version, that's good news, I think.
>
> Cheers,
>
> Dave.
Thanks
Stanislaw Gruszka
prev parent reply other threads:[~2008-03-26 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 14:20 BUG: xfs on linux lvm - lvconvert random hungs when doing i/o Stanislaw Gruszka
2008-03-21 17:45 ` Josef 'Jeff' Sipek
2008-03-22 10:20 ` Stanislaw Gruszka
2008-03-24 23:39 ` David Chinner
2008-03-25 2:02 ` David Chinner
2008-03-26 14:02 ` Stanislaw Gruszka [this message]
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=200803261502.19930.stf_xl@wp.pl \
--to=stf_xl@wp.pl \
--cc=dgc@sgi.com \
--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