linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rupert THURNER <rupert.thurner@gmail.com>
To: Sergei Trofimovich <slyich@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: cannot remove files: "rm" gives "no space left on device", 3.2.0-24, ubuntu
Date: Sun, 17 Jun 2012 06:14:31 +0200	[thread overview]
Message-ID: <CAJs9aZ_C5CzyuudeUg585M4SifunchrmVDg5rXQoo7kDAsOMpw@mail.gmail.com> (raw)
In-Reply-To: <CAJs9aZ-9EK2HUuvBDuiPSG2O5J16seO6Hp3=wJLYAJBi9KDL+Q@mail.gmail.com>

On Sat, Jun 16, 2012 at 2:01 PM, rupert THURNER
<rupert.thurner@gmail.com> wrote:
> On Sat, Jun 16, 2012 at 1:57 PM, Sergei Trofimovich <slyich@gmail.com> wrote:
>> On Sat, 16 Jun 2012 13:16:09 +0200
>> rupert THURNER <rupert.thurner@gmail.com> wrote:
>>
>>> how would i be able to delete something off this btrfs partition
>>> again? i saw the following messages in the archives which seem to be a
>>> little similar ... except a reboot and therfor a remount did not help:
>>> * http://article.gmane.org/gmane.linux.kernel/1265666/match=enospc
>>>
>>> rt@tv:~$ rm -rf /media/388gb-data/.Trash-1000/info/foto.trashinfo
>>> rm: cannot remove `/media/388gb-data/.Trash-1000/info/foto.trashinfo':
>>> No space left on device
>>>
>>> rt@tv:~$ btrfs filesystem df /media/388gb-data/
>>> Data: total=260.59GB, used=254.56GB
>>> System: total=32.00MB, used=24.00KB
>>> Metadata: total=128.00GB, used=120.01GB
>>
>> Looks like there is a bit of space.
>> Try to mount with
>>    '-onospace_cache,clear_cache,enospc_debug'
>> and check if it still reports an ENOSPC error.
> still same error.
>
>> Will result in anything reported in 'dmesg' output?
> [ 6431.514454] device label 388gb-data devid 1 transid 1086 /dev/sda6
> [ 6431.514969] btrfs: disabling disk space caching
> [ 6431.514977] btrfs: force clearing of disk cache
tried the same with kernel versions from
http://kernel.ubuntu.com/~kernel-ppa/mainline/:
* 3.2.20
* 3.4.0
with version 3.4.0, i could delete one tiny file, but only one. peter
mentioned before to run the rm as root. yes, i did that, with all
kernel versions, the error was the same all the time.

  reply	other threads:[~2012-06-17  4:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-16 11:16 cannot remove files: "rm" gives "no space left on device", 3.2.0-24, ubuntu rupert THURNER
2012-06-16 11:18 ` Andrei Popa
2012-06-16 11:26   ` Hugo Mills
2012-06-16 11:46     ` Peter Maloney
2012-06-16 11:57 ` Sergei Trofimovich
2012-06-16 12:01   ` rupert THURNER
2012-06-17  4:14     ` rupert THURNER [this message]
2012-06-17  5:19       ` Andrei Popa
2012-06-17  8:04         ` rupert THURNER
2012-06-17 13:32           ` Mitch Harder
2012-06-17 19:54             ` rupert THURNER
2012-06-18  5:53               ` Goffredo Baroncelli
     [not found]                 ` <CAJs9aZ-GHtO3JsvNqLip9CRXxg_J8RUDM=F7GLfdSqCt-zvB3w@mail.gmail.com>
2012-06-18 16:47                   ` Goffredo Baroncelli
2012-06-18 21:54                     ` Duncan

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=CAJs9aZ_C5CzyuudeUg585M4SifunchrmVDg5rXQoo7kDAsOMpw@mail.gmail.com \
    --to=rupert.thurner@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=slyich@gmail.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;
as well as URLs for NNTP newsgroup(s).