From: Eric Sandeen <sandeen@sandeen.net>
To: "Linda A. Walsh" <xfs@tlinx.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfs_fsr: XFS_IOC_SWAPEXT failed : busy?m
Date: Tue, 20 Oct 2009 17:04:05 -0500 [thread overview]
Message-ID: <4ADE33D5.6080907@sandeen.net> (raw)
In-Reply-To: <4ADD4D9B.9090808@tlinx.org>
Linda A. Walsh wrote:
> 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
>
What kernel? and what file is inode 16781994? (find / -inum 16781994)
EINVAL can come from many places; trying to defrag a swapfile is one of
them ...
-Eric
>
> 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
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-10-20 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 5:41 xfs_fsr: XFS_IOC_SWAPEXT failed : busy?m Linda A. Walsh
2009-10-20 22:04 ` Eric Sandeen [this message]
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=4ADE33D5.6080907@sandeen.net \
--to=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
--cc=xfs@tlinx.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.