All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Vandegrift <ross@willow.seitz.com>
To: Kuba Ober <kuba@mareimbrium.org>
Cc: reiserfs-list@namesys.com
Subject: Re: Scrambled Files
Date: Wed, 24 Apr 2002 14:42:31 -0400	[thread overview]
Message-ID: <20020424184231.GA7963@willow.seitz.com> (raw)
In-Reply-To: <200204240826.09390.kuba@mareimbrium.org>

> > (probably in cache somewhere) 2) being written.
> >
> > For example, apt-get was messing around with xfs when it died.  xfs was
> > completely hosed, as were a bunch of things related to X.  However, the
> > files were hosed with completely non-deterministic contents - german
> > text, what appeared to be UUEncoded binaries, random data, as well as
> > some kind of regular-looking data.  It wasn't like a bunch of the writes
> > got crossed and files ended up backwards.  It also wasn't like random
> > junk was written.
> 
> What you see might be a result of metadata corruption rather than file 
> contents corruption. The metadata might be pointing to astray places, which 
> are either used or unused-but-previously-written-to places on the drive. It 
> may even be that the data from original files is sitting there intact.
> 
> As a side note: did you try fsck'ing the filesystem?
> 
> Cheers,
> Kuba

No, I figured this would probably fix the problems - unfortunately, the
machine's availability is pretty important.  So instead of gambling on
fsck (which the reiserfs devottee in me wanted to do), I started going
about restoring the system from backups and original media (as the
employee in me knew had to be done ::-)

Ross

      reply	other threads:[~2002-04-24 18:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23 21:05 Scrambled Files Ross Vandegrift
2002-04-23 21:46 ` Michael Carmack
2002-04-23 23:02   ` Hans Reiser
2002-04-24  3:32     ` Ross Vandegrift
2002-04-24 12:26       ` Kuba Ober
2002-04-24 18:42         ` Ross Vandegrift [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=20020424184231.GA7963@willow.seitz.com \
    --to=ross@willow.seitz.com \
    --cc=kuba@mareimbrium.org \
    --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.