public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: wildcat <wildcat@espix.org>
To: xfs@oss.sgi.com
Subject: XFS "no space left" problem
Date: Sat, 3 Feb 2007 19:37:23 +0100	[thread overview]
Message-ID: <20070203183723.GA1652@dunno.espix.org> (raw)

Hi dear list,


I recently migrated a 1.3Tbyte partition from reiserfs to XFS.
As the 1.3Tb partition was full, my idea was to shrink reiserfs
partition of 100Gig at a time, and then grow the XFS one.

This has been working since 1.1To for XFS partition. Now I'm in the
following situation:


/dev/mapper/crypt-data
                      1.2T  1.1T  134G  89% /jail2

dunno jail2 # touch a
dunno jail2 # touch b 
touch: cannot touch `b': No space left on device
dunno jail2 # 


>From there if I delete 'a', I could create a file of any size. but then
will be running
again into the "no space left".

>From here, some people told me of an inodes problem, that I checked
first:
/dev/mapper/crypt-data
                     561850144  158335 561691809    1% /jail2

is outputing from df -i.

umount/remount of the partition doesn't change anything. 


here are some information about the filesystem details:


dunno jail2 # xfs_info /jail2
meta-data=/dev/crypt/data        isize=256    agcount=188,
agsize=1638400 blks
         =                       sectsz=512   attr=0
data     =                       bsize=4096   blocks=306708480,
imaxpct=25
         =                       sunit=0      swidth=0 blks, unwritten=1
naming   =version 2              bsize=4096  
log      =internal               bsize=4096   blocks=12800, version=1
         =                       sectsz=512   sunit=0 blks
realtime =none                   extsz=65536  blocks=0, rtextents=0

dunno / # xfs_db /dev/crypt/data 
xfs_db> frag
actual 140099, ideal 134926, fragmentation factor 3.69%
xfs_db> freesp
   from      to extents  blocks    pct
      1       1     801     801   0.00
      2       3       2       5   0.00
     32      63       2      89   0.00
    128     255       3     517   0.00
    256     511       4    1676   0.00
    512    1023       5    3776   0.01
   1024    2047       7   10765   0.03
 262144  524287      23 9200216  26.21
1048576 1638400      16 25888649  73.74
xfs_db> 


I can't think of a Fix solution from here and I'm stuck.

As this box is in production and remotely managed; Go to the
place, take the hard drives and backup/restore is not a solution.

Any help/comment/fix/idea would be very appreciated.
Any additionnal information you need could be asked :)


TIA,
Best regards,



wildcat

             reply	other threads:[~2007-02-03 19:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-03 18:37 wildcat [this message]
2007-02-03 23:38 ` XFS "no space left" problem David Chinner
2007-02-05 17:58   ` Bernd Schubert
2007-02-05 18:28     ` Eric Sandeen
2007-02-05 21:59       ` Bernd Schubert

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=20070203183723.GA1652@dunno.espix.org \
    --to=wildcat@espix.org \
    --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