xfs on armv5 still with erroneous log in kernel 2.6.35.4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello XFS mailinglist,

On my armv5 device I like to use XFS for my simple home made nas, because I think it is ideal for low/medium performance CPUs.
I searched the mailing archive about the usage of XFS on arm architecture. I figured out, that the patchset of James Bottomley was applied to the main line. So I expected xfs to run properly on arm. Unfortunatly I still run into this (known) error after writing some data on an xfs partition and remounting it:
"
SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
SGI XFS Quota Management subsystem
XFS mounting filesystem sda1
Starting XFS recovery on filesystem: sda1 (logdev: internal)
XFS: xlog_recover_process_data: bad clientid
XFS: log mount/recovery failed: error 5
XFS: log mount failed
"

Am I still forced to use the "hammer" approach (flushing buffers in xfs_buf.c) which was proposed in January 2010? Or did I misinterpret the logfile of the xfs component in the kernel (so no arm fixing patches were applied)?

Is xfs NOW be known to work on arm (e.g. armv5)? If so I like to complain. If not, I'm willing to test patches which might solve this issue.

Thanks for reading and any comment,
Ossy
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs

[Index of Archives]     [Linux XFS Devel]     [Linux Filesystem Development]     [Filesystem Testing]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux