From: Gavin Peters <gpeters@deepsky.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Gavin Peters <gpeters@deepsky.com>, xfs@oss.sgi.com
Subject: Re: reservation ran out?
Date: Sun, 6 Sep 2009 08:17:19 -0400 [thread overview]
Message-ID: <20090906121719.GV22496@outrider> (raw)
In-Reply-To: <4AA334AA.9050908@sandeen.net>
On Sat, Sep 05, 2009 at 11:03:54PM -0500, Eric Sandeen wrote:
> Gavin Peters wrote:
>> I just created bug 849, about a reservation problem I'm seeing
>> on my x86_64 system on ubuntu jaunty (2.6.28-15-generic).
>>
>> http://oss.sgi.com/bugzilla/show_bug.cgi?id=849
>>
>> Am I doin' something wrong, or is this a real problem?
>
> Sounds like a real problem.
>
> Any reproducible testcase?
>
Alas, no; I was running mythtv, and my disk was somewhat fragmented.
root@mythmaker:~# xfs_db -c frag -r /dev/sda7
actual 17379, ideal 98, fragmentation factor 99.44%
root@mythmaker:~# xfs_db -c frag -r /dev/sdb1
actual 4268, ideal 53, fragmentation factor 98.76%
The disk that was having the trouble was sda7, my sdb1 was fine.
Mythtv fragments disks so badly by appending to two, or three files,
simultaniously and fsyncing on them a lot. Perhaps some hacking at
that will give a reproduction, I'll see if I can take the time and do
that.
I've since defragmented both disks though; and I've set a large
allocsize (512m) to prevent future fragmentation. We'll see if I get
another crash.
- Gavin
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-09-06 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-05 16:11 reservation ran out? Gavin Peters
2009-09-06 4:03 ` Eric Sandeen
2009-09-06 12:17 ` Gavin Peters [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=20090906121719.GV22496@outrider \
--to=gpeters@deepsky.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