From: Dave Chinner <david@fromorbit.com>
To: Marcus Osdoba <marcus.osdoba@googlemail.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: xfs on armv5 still with erroneous log in kernel 2.6.35.4
Date: Thu, 9 Sep 2010 16:45:24 +1000 [thread overview]
Message-ID: <20100909064524.GA7032@dastard> (raw)
In-Reply-To: <4C87D793.8000103@googlemail.com>
On Wed, Sep 08, 2010 at 08:36:03PM +0200, Marcus Osdoba wrote:
> Am 08.09.2010 09:43, schrieb Dave Chinner:
> >mount -t xfs /dev/sda1 /data
> >cp /bin/sh /data
> >sync
> >umount /data
> >xfs_printlog /dev/sda1
> #no ERROR entry visible
Again, can you pleae paste the entire logprint output here? I'm
asking for _exactly_ what is in your terminal as a result of the
commands you ran. That is, if everything is working correctly, I
would expect you to be pasting in something like this:
# mount /dev/vdb /mnt/scratch
# cp /bin/sh /mnt/scratch
# sync
# umount /mnt/scratch
# xfs_logprint -t /dev/vdb
xfs_logprint:
data device: 0xfd10
log device: 0xfd10 daddr: 10485792 length: 20480
log tail: 6924 head: 6924 state: <CLEAN>
#
If it is different to this, then those differences might
tell me is going wrong. but without the exact commands and output,
I cannot help you....
> # The following command chain trys to reproduce the error
> >mount -t xfs /dev/sda1 /data
> >cp /bin/* /data
> >sync
> Device or resource busy.
This should not be occurring. What is generating this error? is
there anything in your logs/dmesg, etc that indicates what might be
the cause? This is the error that we need to understand first...
> My expectations:
> - sync should never be mandatory before unmounting to keep the FS
> clean (any FS)
It's not. I asked you to run it first to separate writeback from the
unmount process to determine if it was writeback that was having
problems. Clearly, if sync is triggering an error, then the problem
is realted to writeback, and not unmount.
FYI: Without a sync, you should still see a clean log:
# mount /dev/vdb /mnt/scratch
# cp /bin/* /mnt/scratch
# umount /mnt/scratch
# xfs_logprint -t /dev/vdb
xfs_logprint:
data device: 0xfd10
log device: 0xfd10 daddr: 10485792 length: 20480
log tail: 8703 head: 8703 state: <CLEAN>
#
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-09-09 6:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-05 8:52 xfs on armv5 still with erroneous log in kernel 2.6.35.4 Marcus Osdoba
2010-09-06 0:52 ` Dave Chinner
2010-09-06 3:24 ` Eric Sandeen
2010-09-06 18:37 ` Marcus Osdoba
2010-09-07 6:03 ` Dave Chinner
2010-09-07 21:55 ` Marcus Osdoba
2010-09-08 7:43 ` Dave Chinner
2010-09-08 18:36 ` Marcus Osdoba
2010-09-09 6:45 ` Dave Chinner [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=20100909064524.GA7032@dastard \
--to=david@fromorbit.com \
--cc=marcus.osdoba@googlemail.com \
--cc=sandeen@sandeen.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