From: "Huszár Viktor Dénes" <hvd@dwo.hu>
To: 'Emmanuel Florac' <eflorac@intellique.com>, xfs@oss.sgi.com
Subject: RE: free space problem
Date: Thu, 29 May 2008 15:26:16 +0200 [thread overview]
Message-ID: <20080529132624.E3CDCC0D418@cuda.sgi.com> (raw)
In-Reply-To: <20080529125509.136aa653@harpe.intellique.com>
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!!!!
Viktor
-----Original Message-----
From: Emmanuel Florac [mailto:eflorac@intellique.com]
Sent: Thursday, May 29, 2008 12:55 PM
To: xfs@oss.sgi.com
Cc: Huszár Viktor Dénes
Subject: Re: free space problem
Le Thu, 29 May 2008 12:29:25 +0200
Emmanuel Florac <eflorac@intellique.com> écrivait:
> Is it mounted with the inode64 option?
You should try it then. You must unmount it and remount it for this to
take effect. Either add "inode64" to the option line in /etc/fstab, or
use mount -t xfs -o inode64 /some/device /some/mountpoint
--
----------------------------------------
Emmanuel Florac | Intellique
----------------------------------------
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 3143 (20080529) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 3143 (20080529) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
next prev parent reply other threads:[~2008-05-29 13:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080331093951.100ec125@galadriel.home>
2008-03-31 17:36 ` free space problem Huszár Viktor Dénes
2008-04-01 0:35 ` David Chinner
2008-04-01 3:08 ` Huszár Viktor Dénes
2008-04-06 16:09 ` Huszár Viktor Dénes
2008-04-06 16:26 ` KELEMEN Peter
2008-04-06 16:38 ` Huszár Viktor Dénes
2008-04-07 2:18 ` David Chinner
2008-05-29 10:20 ` Huszár Viktor Dénes
2008-05-29 10:29 ` Emmanuel Florac
2008-05-29 10:55 ` Emmanuel Florac
2008-05-29 13:26 ` Huszár Viktor Dénes [this message]
2008-05-29 14:57 ` Dave Chinner
2008-05-29 17:37 ` Huszár Viktor Dénes
[not found] ` <20080529132624.19286105D9@mailwash5.pair.com>
2008-05-29 13:30 ` Emmanuel Florac
2008-03-30 20:29 Huszár Viktor Dénes
2008-03-30 21:54 ` Emmanuel Florac
2008-03-31 0:31 ` Huszár Viktor Dénes
2008-03-31 0:38 ` David Chinner
2008-03-31 17:43 ` Huszár Viktor Dénes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080529132624.E3CDCC0D418@cuda.sgi.com \
--to=hvd@dwo.hu \
--cc=eflorac@intellique.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox