From: John <geearf@free.fr>
To: reiserfs-devel@vger.kernel.org
Subject: No space left on rfs4
Date: Fri, 29 Feb 2008 17:45:55 +0100 [thread overview]
Message-ID: <656df51f9a130e6a80976de1dde9d07f@free.fr> (raw)
Hello people,
I've been following this list for some time but this is my first e-mail here since at least 2 years.
(thank you Edwards for your work, you've fixed many of my issues lately)
Today I am mailing you about an issue that you probably know about, but that I still believe needs to be fixed: filling the FS till it corrupts itself.
How many times have I almost killed by computer by filling my rfs4, copying data on the wrong partition or doing something else...
The FS needs to be able to handle that, but instead some files get corrupted and when I try to delete them my computer is kind of dead and needs to reboot. Of course, I cannot reboot and have to shut it down myself which might corrupt even more data... If I tried to delete some files after filling the partition, at the reboot they're back and so I'm again with a couple of Kb free. Usually a fsck fixes this problem, but when I do that on / the fsck may not be usable anymore...
Don't we have like 5% of space blocked for this case like on other FS? or something else that would prevent this problem from happening?
I am using the latest rfs4 patch from here with a 2.6.24 kernel and a ccreg40 partition, but this issue has been here for years so nothing new I believe.
Thank you,
John
next reply other threads:[~2008-02-29 16:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 16:45 John [this message]
2008-03-01 21:27 ` No space left on rfs4 Edward Shishkin
2008-03-01 21:50 ` John
2008-03-01 22:54 ` Edward Shishkin
2008-03-01 23:05 ` John
2008-03-02 10:17 ` Edward Shishkin
2008-03-02 21:53 ` John
2008-03-02 22:39 ` Christopher Sawtell
2008-03-03 20:59 ` Reiser4 resize John
2008-03-08 19:24 ` No space left on rfs4 Edward Shishkin
2008-03-11 21:39 ` Edward Shishkin
2008-03-11 22:19 ` John
2008-03-12 0:06 ` Edward Shishkin
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=656df51f9a130e6a80976de1dde9d07f@free.fr \
--to=geearf@free.fr \
--cc=reiserfs-devel@vger.kernel.org \
/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).