From: Hans Reiser <reiser@namesys.com>
To: Vitaly Fertman <vitaly@namesys.com>
Cc: Bob Vincent <bobvin@pillars.net>, reiserfs-list@namesys.com
Subject: Re: fsck.reiser4 errors
Date: Wed, 25 Feb 2004 16:35:15 +0300 [thread overview]
Message-ID: <403CA493.3010508@namesys.com> (raw)
In-Reply-To: <200402251531.58759.vitaly@namesys.com>
Vitaly Fertman wrote:
>Hello,
>
>On Wednesday 25 February 2004 02:41, Bob Vincent wrote:
>
>
>>I've been playing around with reiser4 on a non-critical machine at work,
>>and managed to corrupt a 20-gig reiser4 partition.
>>
>>I've run fsck.reiser4 several times to no avail; finally downloaded
>>and compiled the 2.6.3-internal-testing-going-on version of the utils.
>>
>>(much later...)
>>
>>Well, unlike the other versions; this one completed the fsck okay.
>>
>>Just wondering what the following message means?
>>
>> Warning: Can't find stat data extension plugin by its id 0x4.
>>
>>I see it quite often.
>>
>>
>
>If an object is created with some non standard plugins, their ids
>are stored in the special extention of the object stat data. But this
>extention plugin is not ready in the progs yet.
>
>
>
Why is fsck finding non-standard plugins on his computer?
--
Hans
next prev parent reply other threads:[~2004-02-25 13:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 23:41 fsck.reiser4 errors Bob Vincent
2004-02-25 12:31 ` Vitaly Fertman
2004-02-25 13:35 ` Hans Reiser [this message]
2004-02-25 14:42 ` Vitaly Fertman
2004-02-25 19:01 ` Hans Reiser
2004-02-25 21:53 ` Vitaly Fertman
-- strict thread matches above, loose matches on Subject: below --
2003-12-13 18:02 Jedi Ninja
2003-12-15 13:35 ` Vitaly Fertman
2003-12-16 3:10 ` David Masover
2003-12-16 3:28 ` Hans Reiser
2003-12-16 8:23 ` Nikita Danilov
2003-12-16 11:13 ` Vitaly Fertman
2003-12-16 12:30 ` Hans Reiser
[not found] ` <200312151657.58459.vitaly@namesys.com>
2003-12-20 17:24 ` Jedi Ninja
2003-12-22 12:08 ` Vitaly Fertman
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=403CA493.3010508@namesys.com \
--to=reiser@namesys.com \
--cc=bobvin@pillars.net \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@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.