Re: [XFS] xfs_repair time how long it takes??

[Ryan Lee <ryanlee.lahk@xxxxxxxxx>]

Eric,

I have one more qustion for  you.

 

You told me like this "then I would suspect a misconfiguration (maybe mounting -o nobarrier with write caches enabled on the drives?) "

 

How can I check this misconfiguration? such as "-o nobarrier" is I couldn't find this option with mount in my busybox and what do you mean the sentence this " write caches enabled on the drives?"

 

Thanks,

 

On Sat, Mar 3, 2012 at 12:48 AM, Ryan Lee <ryanlee.lahk@xxxxxxxxx> wrote:

Hi, all.

 

Thanks a lot of your kindness for me.

I really realy appreciate it.

 

I am going to tell you what I have done so far porting  XFS in our system.

 

First of all, the resources of our system.

 

CPU : MIPS

KERNEL : 2.6.37-2.6

XFSPROGS : 3.1.7

 

Second, I did this step.

 

1. mounting an xfs filesystem after an unclean shutdown on a machine.

As a result i saw this error below.

------------------------------------------------------------------------

XFS: xlog_recover_process_data: bad clientid
XFS: log mount/recovery failed: error 5
XFS: log mount failed

------------------------------------------------------------------------

 

2. I patched for this error 1 from internet.

http://comments.gmane.org/gmane.comp.file-systems.xfs.general/35446

 

I did aging test by my self.

As a result, after one day overnight, the XFS Filesystem crashed.

 

3, I look for another solution for 1 problem. eventually I found using xfs_repair to remove dirty log and recover.

But as i mentioned it, it takes time a lot.

 

You guys told me to use  the "fsck.xfs". but i think it couldn't solve the problem 1 above.

 

Onething more, I already know about the problem with "xfs_repair", but I cound't find any other good solution to fix it until now.

 

How can I fix it?

Please help me.

 

Thanks, Ryan.

 

 

 

On Sat, Mar 3, 2012 at 12:07 AM, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote:

On 3/2/12 8:26 AM, Ryan wrote:
>
> How about the dirty log. I use the xfs_repair because the dirty log must be removed when i mount HDD.
>
> As you know xfs filesystem doen't repair the dirty log so i couldn't mount the HDD after when i do cold reset during writing the HDD. How i can solve this problem?

If mount fails to replay the dirty log after a power loss, then I would suspect a misconfiguration (maybe mounting -o nobarrier with write caches enabled on the drives?) or a bug in your version of xfs, possibly unique to architecture (what architecture is it, what kernel is it, what xfs "porting" did you do?)

-Eric

> Sent from my iPhone.
>
>
>
> On Mar 2, 2012, at 11:01 PM, Brian Candler <B.Candler@xxxxxxxxx> wrote:
>
>> On Fri, Mar 02, 2012 at 10:09:56PM +0900, Ryan Lee wrote:
>>>   The problem is the taking time with xfs_repair like this "]# xfs_repair
>>>   -P -L /dev/sda2" is to long to wait in our embedded system and for me,
>>>   so the booing time is increasing around 2 minutes totally.
>>
>> Why do you feel you need to run xfs_repair on every boot? Regular Linux
>> systems do not attempt this, the same as they don't force a full "e2fsck -f"
>> on every boot.
>>
>> http://linux.die.net/man/8/fsck.xfs
>

> _______________________________________________
> xfs mailing list
> xfs@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs
>