On Thu, May 29, 2008 at 03:26:16PM +0200, Huszár Viktor Dénes wrote:
> YES! Finally the problem is solved! Thank you Emmanuel and everyone else!
> After adding inode64 to the mount option [only umount and mount worked, with
> remount it didn't] it works. Although the icount and ifree numbers have not
> changed, we can write to the disk.
>
> Hope this will help anyone who encounters this problem. In the xfs man and
> debian docs we could not find anything about this inode64, so thank you once
> again for the help!!!!
I can think of two places off the top of my head where it is
documented:
Documentation/filesystems/xfs.txt in your local kernel source tree:
inode64
Indicates that XFS is allowed to create inodes at any location
in the filesystem, including those which will result in inode
numbers occupying more than 32 bits of significance. This is
provided for backwards compatibility, but causes problems for
backup applications that cannot handle large inode numbers.
$ man 8 mount
inode64
Indicates that XFS is allowed to create inodes at any location in the
filesystem, including those which will result in inode numbers
occupying more
than 32 bits of significance. This is provided for backwards
compatibility,
but causes problems for backup applications that cannot handle large
inode
numbers.
Cheers,
Dave.
--
Dave Chinner
david@xxxxxxxxxxxxx
|