From: "Linda A. Walsh" <xfs@tlinx.org>
To: xfs-oss <xfs@oss.sgi.com>
Subject: xfs_fsr: XFS_IOC_SWAPEXT failed : busy?m
Date: Mon, 19 Oct 2009 22:41:47 -0700 [thread overview]
Message-ID: <4ADD4D9B.9090808@tlinx.org> (raw)
I noticed a weird message from my daily fsr run -- looks like it is on the
root partition.
Does this mean the file was busy? (hopefully? :-))
(all 10 passes...but they were only about 2 seconds apart...disks are
apparently not very frag'ed... :-))...
tnx,
-linda
Oct 19 02:05:33 Ishtar fsr[20913]: / start inode=0
Oct 19 02:05:33 Ishtar fsr[20906]: XFS_IOC_SWAPEXT failed: ino=16781994: Invalid argument
Oct 19 02:05:33 Ishtar fsr[20907]: /var start inode=0
...
Oct 19 02:05:35 Ishtar fsr[20913]: / start inode=0
Oct 19 02:05:35 Ishtar fsr[20913]: XFS_IOC_SWAPEXT failed: ino=16781994: Invalid argument
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-10-20 5:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 5:41 Linda A. Walsh [this message]
2009-10-20 22:04 ` xfs_fsr: XFS_IOC_SWAPEXT failed : busy?m Eric Sandeen
2009-10-21 2:15 ` xfs_fsr: XFS_IOC_SWAPEXT failed; & miscellania Linda A. Walsh
2009-10-21 2:18 ` Eric Sandeen
2009-10-21 2:25 ` Linda A. Walsh
2009-10-21 2:28 ` Eric Sandeen
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=4ADD4D9B.9090808@tlinx.org \
--to=xfs@tlinx.org \
--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