From: Sagar Borikar <sagar_borikar@pmc-sierra.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Nathan Scott <nscott@aconex.com>, xfs@oss.sgi.com
Subject: Re: Xfs Access to block zero exception and system crash
Date: Thu, 03 Jul 2008 10:44:59 +0530 [thread overview]
Message-ID: <486C6053.7010503@pmc-sierra.com> (raw)
In-Reply-To: <486C4F89.9030009@sandeen.net>
Eric Sandeen wrote:
> Sagar Borikar wrote:
>
>> Dave Chinner wrote:
>>
>>> On Wed, Jul 02, 2008 at 04:13:11PM +1000, Nathan Scott wrote:
>>>
>
>
>
>>>> You can always try the reverse - replace fs/xfs from your mips build
>>>> tree with the one from the current/a recent kernel. Theres very few
>>>> changes in the surrounding kernel code that xfs needs.
>>>>
>>>>
>>> Eric should be able to comment on the pitfalls in doing this having
>>> tried to backport a 2.6.25 fs/xfs to a 2.6.18 RHEL kernel. Eric -
>>> any comments?
>>>
>>> Cheers,
>>>
>>> Dave.
>>>
>>>
>> Eric, Could you please let me know about bits and pieces that we need to
>> remember while back porting xfs to 2.6.18?
>> If you share patches which takes care of it, that would be great.
>>
>
> http://sandeen.net/rhel5_xfs/xfs-2.6.25-for-rhel5-testing.tar.bz2
>
> should be pretty close. It was quick 'n' dirty and it has some warts
> but would give an idea of what backporting was done (see patches/ and
> the associated quilt series; quilt push -a to apply them all)
>
Thanks a lot Eric. I'll go through it .I am actually trying another
option of regularly defragmenting the file system under stress.
I wanted to understand couple of things for using xfs_fsr utility:
1. What should be the state of filesystem when I am running xfs_fsr.
Ideally we should stop all io before running defragmentation.
2. How effective is the utility when ran on highly fragmented file
system? I saw that if filesystem is 99.89% fragmented, the recovery is
very slow. It took around 25 min to clean up 100GB JBOD volume and after
that system was fragmented to 82%. So I was confused on how exactly the
fragmentation works.
Any pointers on probable optimum use of xfs_fsr?
3. Any precautions I need to take when working with that from data
consistency, robustness point of view? Any disadvantages?
4. Any threshold for starting the defragmentation on xfs?
Thanks
Sagar
> -Eric
>
next prev parent reply other threads:[~2008-07-03 5:14 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 7:03 Xfs Access to block zero exception and system crash Sagar Borikar
2008-06-25 6:48 ` Sagar Borikar
2008-06-25 8:49 ` Dave Chinner
2008-06-26 6:46 ` Sagar Borikar
2008-06-26 7:02 ` Dave Chinner
2008-06-27 10:13 ` Sagar Borikar
2008-06-27 10:25 ` Sagar Borikar
2008-06-28 0:05 ` Dave Chinner
2008-06-28 16:47 ` Sagar Borikar
2008-06-29 21:56 ` Dave Chinner
2008-06-30 3:37 ` Sagar Borikar
[not found] ` <20080630034112.055CF18904C4@bby1mta01.pmc-sierra.bc.ca>
2008-06-30 6:07 ` Sagar Borikar
2008-06-30 10:24 ` Sagar Borikar
2008-07-01 6:44 ` Dave Chinner
2008-07-02 4:18 ` Sagar Borikar
2008-07-02 5:13 ` Dave Chinner
2008-07-02 5:35 ` Sagar Borikar
2008-07-02 6:13 ` Nathan Scott
2008-07-02 6:56 ` Dave Chinner
2008-07-02 11:02 ` Sagar Borikar
2008-07-03 4:03 ` Eric Sandeen
2008-07-03 5:14 ` Sagar Borikar [this message]
2008-07-03 15:02 ` Eric Sandeen
2008-07-04 10:18 ` Sagar Borikar
2008-07-04 12:27 ` Dave Chinner
2008-07-04 17:30 ` Sagar Borikar
2008-07-04 17:35 ` Eric Sandeen
2008-07-04 17:51 ` Sagar Borikar
2008-07-05 16:25 ` Eric Sandeen
2008-07-06 17:24 ` Sagar Borikar
2008-07-06 19:07 ` Eric Sandeen
2008-07-07 3:02 ` Sagar Borikar
2008-07-07 3:04 ` Eric Sandeen
2008-07-07 3:07 ` Sagar Borikar
2008-07-07 3:11 ` Eric Sandeen
2008-07-07 3:17 ` Sagar Borikar
2008-07-07 3:22 ` Eric Sandeen
2008-07-07 3:42 ` Sagar Borikar
[not found] ` <487191C2.6090803@sandeen .net>
[not found] ` <4871947D.2090701@pmc-sierr a.com>
2008-07-07 3:47 ` Eric Sandeen
2008-07-07 3:58 ` Sagar Borikar
2008-07-07 5:19 ` Eric Sandeen
2008-07-07 5:58 ` Sagar Borikar
2008-07-06 4:19 ` Dave Chinner
2008-07-04 15:33 ` Eric Sandeen
2008-06-28 0:02 ` Dave Chinner
[not found] <4872E0BC.6070400@pmc-sierra.com>
[not found] ` <4872E33E.3090107@sandeen.net>
2008-07-08 5:03 ` Sagar Borikar
2008-07-09 16:57 ` Sagar Borikar
2008-07-10 5:12 ` Sagar Borikar
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=486C6053.7010503@pmc-sierra.com \
--to=sagar_borikar@pmc-sierra.com \
--cc=nscott@aconex.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