All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Oleg Drokin <green@namesys.com>
Cc: D_i_F_i@gmx.de, reiserfs-list@namesys.com
Subject: Re: "no space left" but df -k shows plenty of free space
Date: 19 May 2003 13:38:38 -0400	[thread overview]
Message-ID: <1053365917.6207.105.camel@tiny.suse.com> (raw)
In-Reply-To: <20030519160208.GA14048@namesys.com>

On Mon, 2003-05-19 at 12:02, Oleg Drokin wrote:
> Hello!
> 
> On Sat, May 17, 2003 at 05:34:09PM +0200, D_i_F_i@gmx.de wrote:
> > while copying some data into a logical volume with reiserfs as
> > filesystem, I've got an error message, that there isn't enough
> > space left on the device. Even just creating a new empty file
> > isn't possible anymore:
> > sammy:/opt/kgm/data/log # touch abc
> > touch: creating `abc': No space left on device
> > But the df-command has still reported quite a lot of free capacity:
> > sammy:/opt/kgm/data/log # df -k /opt/kgm/data
> > Filesystem        1k-blocks     Used Available Use% Mounted on
> > /dev/kgmvg/datalv  10485436  7987364   2498072  77% /opt/kgm/data
> 
> Hm, this is pretty strange.

Could you please run debugreiserfs -p /dev/xxx | gzip -c >
df-error-fs.gz, and make it available somewhere for us to download.  If
you are using reiserfsprogs 3.x.0j or so the output can contain actual
file data, so you probably want to put the image onto a password
protected page.

This will take a metadata dump of the filesystem, I'd like to check it.

-chris



  parent reply	other threads:[~2003-05-19 17:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-17 15:34 "no space left" but df -k shows plenty of free space D_i_F_i
2003-05-19 16:02 ` Oleg Drokin
2003-05-19 16:10   ` Chris Mason
2003-05-19 17:38   ` Chris Mason [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-19 22:24 D_i_F_i
2003-05-20  9:44 ` Oleg Drokin

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=1053365917.6207.105.camel@tiny.suse.com \
    --to=mason@suse.com \
    --cc=D_i_F_i@gmx.de \
    --cc=green@namesys.com \
    --cc=reiserfs-list@namesys.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.