From: "Marcin Mirosław" <marcin@mejor.pl>
To: Amit Sahrawat <amit.sahrawat83@gmail.com>
Cc: linux-xfs@oss.sgi.com, Marcin M <gmane@mejor.pl>
Subject: Re: tasks hangs in D state while writing to xfs
Date: Sat, 15 Oct 2011 19:45:25 +0200 [thread overview]
Message-ID: <4E99C6B5.6070205@mejor.pl> (raw)
In-Reply-To: <CADDb1s3pG3JPg4nceVjbs4QiCsRY+y+juY_w3eHaup=1KVMC3A@mail.gmail.com>
W dniu 2011-10-15 18:04, Amit Sahrawat pisze:
> Hi Marcin,
> Can you share the Free blocks for the disk at the time of this
> issue(df -k)? It seems that the disk do not have enough free space to
> reserve a transaction.
> Also, the logs also seems to be mixed. The stucked position really seems to be :
> Function: xlog_grant_log_space()
> /* Is there space or do we need to sleep? */
> spin_lock(&log->l_grant_lock);
> Is there any other activity which was done on the disk before you
> observed these hang traces?At first it does seems to hang XFS, next if
> you issue a 'sync' you will observe that sync will also turn to
> TASK_UNINTERRUPTIBLE 'D' state.
Hi Amit.
# df -kT /dev/sda11
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/sda11 xfs 3840937 2354891 1486046 62% /mnt/cdrom
No, i only run rsync to partition located at /dev/sda11. Meseems the
main information is size of log. Maybe there is board case when log is
minimal size (such small as mkfs allow).
Regards.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-10-15 17:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-15 11:54 tasks hangs in D state while writing to xfs Marcin M
2011-10-15 12:28 ` Marcin M
2011-10-15 16:04 ` Amit Sahrawat
2011-10-15 17:45 ` Marcin Mirosław [this message]
2011-10-15 22:09 ` Dave Chinner
2011-10-15 22:16 ` Marcin Mirosław
2011-10-16 11:48 ` Marcin Mirosław
2011-10-16 12:35 ` Christoph Hellwig
2011-10-16 13:38 ` Marcin Mirosław
2011-10-16 16:05 ` Christoph Hellwig
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=4E99C6B5.6070205@mejor.pl \
--to=marcin@mejor.pl \
--cc=amit.sahrawat83@gmail.com \
--cc=gmane@mejor.pl \
--cc=linux-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