reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Magicloud Magiclouds <magicloud.magiclouds@gmail.com>
To: Edward Shishkin <edward.shishkin@gmail.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: Little report on reiser4 with 2.6.35.7
Date: Sat, 13 Nov 2010 20:22:09 +0800	[thread overview]
Message-ID: <AANLkTimnRDC9bARHODueiKMG2f5c8RQ+6zYTnr_AvAxZ@mail.gmail.com> (raw)
In-Reply-To: <4CDE8129.6050708@gmail.com>

On Sat, Nov 13, 2010 at 8:14 PM, Edward Shishkin
<edward.shishkin@gmail.com> wrote:
> Magicloud Magiclouds wrote:
>> Hi,
>>   I compiled 2.6.35.7 kernel with reiser4 patch on debian sid. And I
>> found a serious problem. When the reiser4 fs was full, it broke down,
>> which lead the module to "bus error". Then I fscked it, I had to "fix"
>> and "build file system". At last, I lost some files (not sure of the
>> contents of the left files), which are not created right before it
>> broke down.
>>
>
> Yes, I have reproduced some problems, when running out of disk space.
> It seems ENOSPC is handled incorrectly, and there is a problem in reading
> (partially converted) files. I'll take a look..
>
> Thanks,
> Edward.
>

Glad to hear that. Hoping it will be resolved soon.

PS: May I know when would the patch for 2.6.36 be released?

-- 
竹密岂妨流水过
山高哪阻野云飞
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2010-11-13 12:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12  7:54 Little report on reiser4 with 2.6.35.7 Magicloud Magiclouds
2010-11-12 11:34 ` Edward Shishkin
2010-11-12 12:26   ` Magicloud Magiclouds
2010-11-16 13:42     ` Edward Shishkin
2010-11-13 12:14 ` Edward Shishkin
2010-11-13 12:22   ` Magicloud Magiclouds [this message]

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=AANLkTimnRDC9bARHODueiKMG2f5c8RQ+6zYTnr_AvAxZ@mail.gmail.com \
    --to=magicloud.magiclouds@gmail.com \
    --cc=edward.shishkin@gmail.com \
    --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).