All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
To: Vitaly Fertman <vitaly@namesys.com>
Cc: "Raymond A. Meijer" <rmeijer@internet.gr>, reiserfs-list@namesys.com
Subject: Re: fsck.reiser4 can't fix 1 fixable corruption
Date: Wed, 21 Apr 2004 14:05:12 +0200	[thread overview]
Message-ID: <40866378.3030009@gmx.net> (raw)
In-Reply-To: <200404211547.08993.vitaly@namesys.com>

Vitaly Fertman wrote:
> On Wednesday 21 April 2004 13:59, Raymond A. Meijer wrote:
> 
>>On Wed 21 April 2004 11:55, Vitaly Fertman wrote:
>>
>>>would you try this patch, it should fix the problem,
>>>email me about the result please.
>>
>>No luck... :(
> 
> 
> ok, that patch avoids such problems if you have not fsck'ed yet.

The patch didn't apply in the first place, so it of course couldn't work
(see Raymonds earlier mail).


> I have put another internal reiser4progs snapshot with some more 
> fixes into the www.namesys.com/snapshots/2004.04.21-internal.testing/
> I have no problems with it, try it please.


Carl-Daniel
-- 
http://www.hailfinger.org/


  reply	other threads:[~2004-04-21 12:05 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-20 14:33 fsck.reiser4 can't fix 1 fixable corruption Raymond A. Meijer
2004-04-20 18:54 ` Sander Sweers
2004-04-21  8:09   ` Raymond A. Meijer
2004-04-21  8:55 ` Vitaly Fertman
2004-04-21  9:11   ` Raymond A. Meijer
2004-04-21  9:59   ` Raymond A. Meijer
2004-04-21 11:51     ` Vitaly Fertman
2004-04-21 12:05       ` Carl-Daniel Hailfinger [this message]
2004-04-21 12:09       ` Raymond A. Meijer
2004-04-21 12:19         ` Sander Sweers
2004-04-21 19:30           ` Sander Sweers
2004-04-21 19:44             ` Domenico Andreoli
2004-04-21 20:13               ` Sander Sweers
2004-04-21 20:53                 ` Domenico Andreoli
2004-04-21 21:13                   ` Vitaly Fertman
2004-04-21 21:58                     ` Domenico Andreoli
2004-04-22 10:46                       ` Vitaly Fertman
2004-04-22 11:44                         ` Domenico Andreoli
2004-04-23  9:15                           ` Vitaly Fertman
2004-04-23 20:19                             ` Hans Reiser
2004-04-23 20:59                               ` Vitaly Fertman
2004-04-24  0:00                                 ` Hans Reiser
2004-04-22 12:37                         ` Domenico Andreoli
2004-04-22 17:51                           ` Hans Reiser
2004-04-22 18:30               ` Hans Reiser
2004-04-23  1:22                 ` Domenico Andreoli
2004-04-25 16:31                   ` Hans Reiser
2004-04-25 20:31                     ` Domenico Andreoli
2004-04-30  3:16                       ` Hans Reiser
2004-04-30 10:18                         ` Vitaly Fertman
2004-04-28  9:09                     ` Vitaly Fertman
2004-04-23  7:04                 ` Yury Umanets
2004-04-23  9:03                   ` Vitaly Fertman
2004-04-23 10:27                     ` Domenico Andreoli
2004-04-23 12:54                       ` Vitaly Fertman
2004-04-23 11:01                     ` Yury Umanets
2004-04-21 13:30       ` reiser4progs 0.5.4 build error (was Re: fsck.reiser4 can't fix 1 fixable corruption) Domenico Andreoli

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=40866378.3030009@gmx.net \
    --to=c-d.hailfinger.kernel.2004@gmx.net \
    --cc=reiserfs-list@namesys.com \
    --cc=rmeijer@internet.gr \
    --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.