From: Edward Shishkin <edward.shishkin@gmail.com>
To: Dushan Tcholich <dusanc@gmail.com>
Cc: "Mr. Tao" <tao@post.cz>,
Reiserfs mailing list <reiserfs-devel@vger.kernel.org>
Subject: Re: kernel BUG at fs/reiser4/plugin/item/ctail.c
Date: Mon, 04 Aug 2008 20:50:06 +0400 [thread overview]
Message-ID: <4897333E.3030600@gmail.com> (raw)
In-Reply-To: <a08621850808040757h2f421e38lc295fb54fc719687@mail.gmail.com>
Dushan Tcholich wrote:
> On Mon, Aug 4, 2008 at 4:47 PM, Edward Shishkin
> <edward.shishkin@gmail.com> wrote:
>
>> Dushan Tcholich wrote:
>>
>>> Would it be possible if there would be a new version of fsck.reiser4
>>> to fix those false positives about wrong size when checking
>>> cryptocompress partitions?
>>>
>>>
>> Yes, per-file warnings about wrong i_bytes should be suppressed.
>> Fsck just should report at the end of work in default mode, that N wrong
>> i_bytes were detected and suggest to fix it with --fix option.
>> Anyone care to try to make a patch?
>>
>>
> But what happens with systems with ccreg and fsck on boot? They would
> stop and wait for user interaction.
>
Why?
Do you have any problems with boot?
> Or you meant just to print a message about it with recomended solution
> and continue.
>
Everything should be the same except per-file warnings.
> I'd like to make a patch but dunno how :)
>
>
>>> There are some users that reported those and it's not comforting when
>>> your fs spews thousands of errors, even when someone tells you they're
>>> false.
>>>
>>> Oh and what about making cryptocompress default format on mkfs.reiser4 ?
>>>
>>>
>> mm.. not sure. First, fsck should be fixed to remove unprepped items.
>>
> Ofcourse.
>
>
>> Mr. Tao, do you still have partitions that make fsck segfault?
>>
>> Thanks,
>> Edward.
>>
>>
> Dushan
>
>
next prev parent reply other threads:[~2008-08-04 16:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <558.1643-13003-1386678025-1217242012@post.cz>
2008-07-28 14:31 ` kernel BUG at fs/reiser4/plugin/item/ctail.c Edward Shishkin
2008-08-04 10:28 ` Dushan Tcholich
2008-08-04 14:47 ` Edward Shishkin
2008-08-04 14:57 ` Dushan Tcholich
2008-08-04 16:50 ` Edward Shishkin [this message]
2008-08-04 21:57 ` Dushan Tcholich
2008-08-04 22:51 ` Volker Armin Hemmann
2008-08-05 20:31 ` Edward Shishkin
2008-08-05 12:42 ` Mr. Tao
2008-08-07 18:54 ` [reiser4] Point Ryan Hope
2008-08-08 20:47 ` Edward Shishkin
2008-08-09 15:03 ` Ryan Hope
2008-08-12 18:58 ` Edward Shishkin
2008-08-12 20:05 ` Matthew
2008-08-12 20:47 ` Edward Shishkin
2008-08-13 8:43 ` Matthew
2008-08-13 9:57 ` Edward Shishkin
2008-08-13 15:03 ` Ryan Hope
2008-08-13 15:59 ` Alli Quaknaa
2008-08-13 16:28 ` Ryan Hope
2008-08-13 16:33 ` Alli Quaknaa
[not found] <558.1643-7112-806549272-1217237371@post.cz>
2008-07-28 14:13 ` kernel BUG at fs/reiser4/plugin/item/ctail.c 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=4897333E.3030600@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=dusanc@gmail.com \
--cc=reiserfs-devel@vger.kernel.org \
--cc=tao@post.cz \
/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.