| To: | Ofer Heifetz <oferh@xxxxxxxxxxx> |
|---|---|
| Subject: | RE: XFS support for ARMv5 |
| From: | Andy Poling <andy@xxxxxxxxxxx> |
| Date: | Wed, 25 Nov 2009 10:30:09 -0600 (CST) |
| Cc: | "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
| In-reply-to: | <EE71107DF0D1F24FA2D95041E64AB9E8985A59F31F@xxxxxxxxxxxxxxxxxxx> |
| References: | <14274282.01258546868484.JavaMail.root@wombat> <4B041AEE.4040506@xxxxxxxxxxx> <EE71107DF0D1F24FA2D95041E64AB9E8985A59F17F@xxxxxxxxxxxxxxxxxxx> <4B096C6E.8010508@xxxxxxxxxxx> <EE71107DF0D1F24FA2D95041E64AB9E8985A59F31F@xxxxxxxxxxxxxxxxxxx> |
| User-agent: | Alpine 2.00 (DEB 1167 2008-08-23) |
On Mon, 23 Nov 2009, Ofer Heifetz wrote: Here is the dmesg I got for mount /dev/sda3 /mnt/usb: SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled XFS mounting filesystem sda3 Starting XFS recovery on filesystem: sda3 (logdev: internal) XFS: xlog_recover_process_data: bad clientid XFS: log mount/recovery failed: error 5 XFS: log mount failed
See this thread in the archives for a patch that may fix this:
http://oss.sgi.com/pipermail/xfs/2009-October/042805.html
-Andy
It ain't what you don't know that gets you into trouble.
It's what you know for sure that just ain't so. - Mark Twain
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: consistency checks, Bill Kendall |
|---|---|
| Next by Date: | [PATCH] xfstests 213: Add enospc case to fallocate test, Eric Sandeen |
| Previous by Thread: | RE: XFS support for ARMv5, Ofer Heifetz |
| Next by Thread: | Re: XFS support for ARMv5, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |