From: Hans Reiser <reiser@namesys.com>
To: Oleg Drokin <green@namesys.com>
Cc: Matthias Andree <ma+rfs@dt.e-technik.uni-dortmund.de>,
reiserfs-list@namesys.com, god@namesys.com,
mason <mason@namesys.com>
Subject: Re: Corruption: --fix-fixable results in all nlink values = 0
Date: Mon, 19 Aug 2002 14:27:59 +0400 [thread overview]
Message-ID: <3D60C82F.1080403@namesys.com> (raw)
In-Reply-To: 20020819142035.A5741@namesys.com
Oleg Drokin wrote:
>Hello!
>
>On Mon, Aug 19, 2002 at 02:07:26PM +0400, Hans Reiser wrote:
>
>
>
>>>He suggests that user should specify list of bad blocks each time user runs
>>>reiserfsck.
>>>
>>>
>>This sounds reasonable. You can probably even have a default location
>>
>>
>
>Not for me.
>
>
>
>>to check for the list somewhere in /etc if you want. Remind the user
>>
>>
>
>File can get corrupted too.
>
>
>
>
>>that you are using it everytime you find it though, that way if a
>>different sysadmin is running fsck, they can know why not all the blocks
>>they expect to be there are accessible.
>>
>>
>
>Having some config files for this purpose is not good.
>What if I have booted from rescue disk?
>
>Bye,
> Oleg
>
>
>
>
That is why it is only the DEFAULT location, and (slight improvement
here) the user is prompted about whether to use it.
next prev parent reply other threads:[~2002-08-19 10:27 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 18:07 Corruption: --fix-fixable results in all nlink values = 0 Gerrit Hannaert
2002-08-15 18:27 ` Vitaly Fertman
2002-08-15 18:36 ` Gerrit Hannaert
2002-08-15 18:53 ` Vitaly Fertman
2002-08-15 19:06 ` Gerrit Hannaert
2002-08-15 19:44 ` Stefan Fleiter
2002-08-15 20:02 ` Gerrit Hannaert
2002-08-16 10:42 ` Matthias Andree
2002-08-16 17:34 ` Vitaly Fertman
2002-08-17 0:18 ` search for mailing archive on geocrawler bo
2002-08-17 1:03 ` Manuel Krause
2002-08-15 21:29 ` Corruption: --fix-fixable results in all nlink values = 0 Gerrit Hannaert
2002-08-16 8:05 ` Vitaly Fertman
2002-08-16 8:59 ` Gerrit Hannaert
2002-08-16 10:50 ` Matthias Andree
2002-08-16 13:11 ` Gerrit Hannaert
2002-08-16 14:12 ` Matthias Andree
2002-08-16 14:24 ` Hans Reiser
2002-08-16 14:42 ` bscott
2002-08-16 14:58 ` Matthias Andree
2002-08-18 21:08 ` Brian Tinsley
2002-08-19 8:38 ` Hans Reiser
2002-08-17 0:54 ` Gerrit Hannaert
2002-08-17 10:00 ` Matthias Andree
2002-08-17 19:00 ` Hans Reiser
2002-08-19 5:20 ` Oleg Drokin
2002-08-19 8:42 ` Hans Reiser
2002-08-19 8:46 ` Oleg Drokin
2002-08-19 9:14 ` Hans Reiser
2002-08-19 9:22 ` Oleg Drokin
2002-08-19 10:07 ` Hans Reiser
2002-08-19 10:20 ` Oleg Drokin
2002-08-19 10:27 ` Hans Reiser [this message]
2002-08-19 10:40 ` Oleg Drokin
2002-08-19 11:14 ` Hans Reiser
2002-08-19 11:20 ` Oleg Drokin
2002-08-19 13:29 ` Hans Reiser
2002-08-19 13:31 ` Oleg Drokin
2002-08-19 13:55 ` Matthias Andree
2002-08-19 14:25 ` Hans Reiser
2002-08-20 20:24 ` Chris Mason
2002-08-21 6:04 ` Oleg Drokin
2002-08-21 10:33 ` Hans Reiser
2002-08-21 16:17 ` Gerrit Hannaert
2002-08-21 17:14 ` Hans Reiser
2002-08-21 17:33 ` Valdis.Kletnieks
2002-08-21 17:36 ` Hans Reiser
2002-08-22 11:00 ` Vitaly Fertman
2002-08-22 12:55 ` Chris Mason
2002-08-22 13:00 ` Oleg Drokin
2002-08-22 16:42 ` Hans Reiser
2002-08-23 4:56 ` Oleg Drokin
2002-08-23 10:53 ` Hans Reiser
2002-08-23 10:56 ` Oleg Drokin
2002-08-23 11:01 ` Hans Reiser
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=3D60C82F.1080403@namesys.com \
--to=reiser@namesys.com \
--cc=god@namesys.com \
--cc=green@namesys.com \
--cc=ma+rfs@dt.e-technik.uni-dortmund.de \
--cc=mason@namesys.com \
--cc=reiserfs-list@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.