<div>Eric, </div><div>I have one more qustion for you.</div><div> </div><div>You told me like this "then I would suspect a misconfiguration (maybe mounting -o nobarrier with write caches enabled on the drives?) " </div>
<div> </div><div>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?"</div>
<div> </div><div>Thanks,</div><div><br><br> </div><div class="gmail_quote">On Sat, Mar 3, 2012 at 12:48 AM, Ryan Lee <span dir="ltr"><<a href="mailto:ryanlee.lahk@gmail.com">ryanlee.lahk@gmail.com</a>></span> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote"><div><br>Hi, all.</div><div> </div><div>Thanks a lot of your kindness for me.</div>
<div>I really realy appreciate it.</div><div> </div><div>I am going to tell you what I have done so far porting XFS in our system.</div><div>
</div><div>First of all, the resources of our system.</div><div> </div><div>CPU : MIPS</div><div>KERNEL : 2.6.37-2.6</div><div>XFSPROGS : 3.1.7</div><div> </div><div>Second, I did this step.</div><div> </div><div>1. mounting an xfs filesystem after an unclean shutdown on a machine.</div>
<div>As a result i saw this error below.</div><div>------------------------------------------------------------------------</div><div>XFS: xlog_recover_process_data: bad clientid<br>XFS: log mount/recovery failed:
error 5<br>XFS: log mount failed</div><div>------------------------------------------------------------------------</div><div> </div><div>2. I patched for this error 1 from internet.</div><div><a href="http://comments.gmane.org/gmane.comp.file-systems.xfs.general/35446" target="_blank">http://comments.gmane.org/gmane.comp.file-systems.xfs.general/35446</a></div>
<div> </div><div>I did aging test by my self. </div><div>As a result, after one day overnight, the XFS Filesystem crashed.</div><div> </div><div>3, I look for another solution for 1 problem. eventually I found using xfs_repair to remove dirty log and recover.</div>
<div>But as i mentioned it, it takes time a lot.</div><div> </div><div>You guys told me to use the "fsck.xfs". but i think it couldn't solve the problem 1 above.</div><div> </div><div>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.</div>
<div> </div><div>How can I fix it?</div><div>Please help me.</div><div> </div><div>Thanks, Ryan.</div><div class="HOEnZb"><div class="h5"><div> </div><div> </div><div><br> </div><div class="gmail_quote">On Sat, Mar 3, 2012 at 12:07 AM, Eric Sandeen <span dir="ltr"><<a href="mailto:sandeen@sandeen.net" target="_blank">sandeen@sandeen.net</a>></span> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote"><div>On 3/2/12 8:26 AM, Ryan wrote:<br>
><br>
> How about the dirty log. I use the xfs_repair because the dirty log must be removed when i mount HDD.<br>
><br>
> 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?<br>
<br>
</div>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?)<br>
<span><font color="#888888"><br>
-Eric<br>
</font></span><div><br>
> Sent from my iPhone.<br>
><br>
><br>
><br>
> On Mar 2, 2012, at 11:01 PM, Brian Candler <<a href="mailto:B.Candler@pobox.com" target="_blank">B.Candler@pobox.com</a>> wrote:<br>
><br>
>> On Fri, Mar 02, 2012 at 10:09:56PM +0900, Ryan Lee wrote:<br>
>>> The problem is the taking time with xfs_repair like this "]# xfs_repair<br>
>>> -P -L /dev/sda2" is to long to wait in our embedded system and for me,<br>
>>> so the booing time is increasing around 2 minutes totally.<br>
>><br>
>> Why do you feel you need to run xfs_repair on every boot? Regular Linux<br>
>> systems do not attempt this, the same as they don't force a full "e2fsck -f"<br>
>> on every boot.<br>
>><br>
>> <a href="http://linux.die.net/man/8/fsck.xfs" target="_blank">http://linux.die.net/man/8/fsck.xfs</a><br>
><br>
</div><div><div>> _______________________________________________<br>
> xfs mailing list<br>
> <a href="mailto:xfs@oss.sgi.com" target="_blank">xfs@oss.sgi.com</a><br>
> <a href="http://oss.sgi.com/mailman/listinfo/xfs" target="_blank">http://oss.sgi.com/mailman/listinfo/xfs</a><br>
><br>
<br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>