From: Alex Elder <aelder@sgi.com>
To: Dave Howorth <dhoworth@mrc-lmb.cam.ac.uk>
Cc: xfs@oss.sgi.com
Subject: Re: no space left on device with 662G free
Date: Wed, 15 Sep 2010 09:30:00 -0500 [thread overview]
Message-ID: <1284561000.2452.1.camel@doink> (raw)
In-Reply-To: <4C90D080.5090004@mrc-lmb.cam.ac.uk>
On Wed, 2010-09-15 at 14:56 +0100, Dave Howorth wrote:
> Hello,
>
> I recently started using XFS when I set up a new server and I'm having a
> problem when copying data on to it from an old server. cp reports errors
> like:
>
> cp: cannot create symbolic link
> `/nfs/scop4/data/trembl/xml/releases/2006-01-10/Q6RXU6.xml': No space
> left on device
Please send the output of this command:
xfs_info /dev/mapper/vg--storage-lv--data
I'm pretty sure you've run out of inodes.
-Alex
> and later
>
> cp: cannot create directory
> `/nfs/scop4/data/trembl/xml/releases/2006-01-24': No space left on device
>
> The filesystem is in a 2 TB LVM on an md RAID and according to df
> there's 662 GB space free:
>
> /dev/mapper/vg--storage-lv--data
> 2.0T 1.4T 662G 68% /nfs/scop4/data
>
> There are a quite a few directories in the filesystem. Some of the
> directories contain many millions of files and some directories consist
> entirely of symlinks, if any of that's relevant.
>
> The filesystem is on a newish machine running openSUSE 11.2 (Linux scop4
> 2.6.31.12-0.2-desktop #1 SMP PREEMPT 2010-03-16 21:25:39 +0100 x86_64
> x86_64 x86_64 GNU/Linux) and the data is being mirrored from an older
> machine that uses a reiser filesystem and which stores the data without
> problem.
>
> Some folks on the suse mailing list said it was probably an inode
> problem and suggested I run df -i:
>
> # df -i /nfs/scop4/data
> Filesystem Inodes IUsed IFree IUse% Mounted on
> /dev/mapper/vg--storage-lv--data
> 429496704 -18446744073280007488
> 18446744073709504192 - /nfs/scop4/data
>
> I don't understand that output, especially the negative number! I then
> read about the inode64 mount option in the XFS FAQ and I believe I've
> now enabled that and remounted the filesystem. mtab shows
>
> /dev/mapper/vg--storage-lv--data /nfs/scop4/data xfs rw,noatime,inode64 0 0
>
> But I'm still seeing the same errors as before. Is there something else
> I need to do to enable inode64, or am I looking in the wrong direction?
>
> Thanks, Dave
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-15 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 13:56 no space left on device with 662G free Dave Howorth
2010-09-15 14:30 ` Alex Elder [this message]
2010-09-15 14:38 ` Dave Howorth
2010-09-15 14:59 ` Michael Weissenbacher
2010-09-15 16:14 ` Dave Howorth
2010-09-15 14:45 ` Andy Bennett
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=1284561000.2452.1.camel@doink \
--to=aelder@sgi.com \
--cc=dhoworth@mrc-lmb.cam.ac.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.