mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: "Saber Taylor" <aquabrake@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: lost dirs after fsck-1.18 (kt133, ide, dma, test10, test11)
Date: Sun, 3 Dec 2000 14:21:47 -0500	[thread overview]
Message-ID: <200012031921.OAA17544@tsx-prime.MIT.EDU> (raw)
In-Reply-To: Saber Taylor's message of Sun, 03 Dec 2000 05:59:47 -0000, <F231OceuLyR1mDxJr5D0000c3f6@hotmail.com>

   From: "Saber Taylor" <aquabrake@hotmail.com>
   Date: 	Sun, 03 Dec 2000 05:59:47 -0000

   Well that's the last time I run a devel kernel with a nontest
   system.  sigh.

   Had one directory replaced with a different directory
   and also a directory replaced with a file. Possible further
   corruption.

   I don't think I lost the directories until I did a 'fsck -y'
   on the partition. Something to remember.

If it was just the directories that got lost, the files should have
been reparented to the /lost+found directory for that filesystrem.  If
however the bug wiped out part of your inode table, then you would have
probably lost both the directory and the files in that directory, since
directories and files tend to be stored in the same block group.

   If anyone has advice on recovering the directories other than
   the following links, I'm all ears:

Without more details about how the corruption happened or what the
nature of the corruption is, it's hard to give good general advice.
Those websites aren't bad places to start.  Good luck.....

						- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      parent reply	other threads:[~2000-12-03 19:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-03  5:59 Saber Taylor
2000-12-03  6:33 ` Mohammad A. Haque
2000-12-03 19:21 ` Theodore Y. Ts'o [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=200012031921.OAA17544@tsx-prime.MIT.EDU \
    --to=tytso@mit.edu \
    --cc=aquabrake@hotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®