From: "Theodore Ts'o" <tytso@mit.edu>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Unix v7 icheck dup problem
Date: Wed, 1 Mar 2023 11:57:01 -0500 [thread overview]
Message-ID: <Y/+D3c5Q8tXfVf0L@mit.edu> (raw)
In-Reply-To: <20230301150905.AA4CD18C07B@mercury.lcs.mit.edu>
On Wed, Mar 01, 2023 at 10:09:05AM -0500, Noel Chiappa wrote:
> To do it, you need to i) understand how the FS works (see:
>
> https://minnie.tuhs.org/cgi-bin/utree.pl?file=V6/usr/man/man5/fs.5
>
> but it's pretty simple); ii) understand what the few tools (dcheck; icheck;
> clri) do; iii) dive in.
In honor of dcheck, icheck, and clri, when I creating debugfs(8) for
ext2/ext3/ext4 file system, I implemented the dcheck, icheck, and clri
commands.
I've been known to use them (and other debugfs commands) from time to
time when someone needs emergency data recovery (say, someone who has
ten years of Ph.D. research without ever doing backups, and then the
file system get scrambled --- although some have argued that if
someone doesn't do backups of their research data, maybe they don't
*deserve* to get their Ph.D. :-)
- Ted
next prev parent reply other threads:[~2023-03-01 16:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 15:09 Noel Chiappa
2023-03-01 16:18 ` Ron Natalie
2023-03-01 16:45 ` KenUnix
2023-03-01 16:57 ` Theodore Ts'o [this message]
2023-03-01 20:52 ` Dave Horsfall
2023-03-02 1:46 ` Jonathan Gray
2023-03-02 3:05 ` Dave Horsfall
2023-03-02 7:56 ` John Cowan
2023-03-02 8:53 ` Steve Nickolas
2023-03-02 8:01 ` Jonathan Gray
2023-03-02 7:34 ` arnold
2023-03-01 21:29 Noel Chiappa
2023-03-01 21:54 ` KenUnix
2023-03-01 21:55 ` John Cowan
2023-03-01 22:15 ` Jon Forrest
2023-03-02 4:16 ` Jonathan Gray
2023-03-02 1:36 Noel Chiappa
2023-03-02 1:56 ` John Cowan
2023-03-02 6:41 ` Lars Brinkhoff
2023-03-02 2:12 ` Bakul Shah
2023-03-02 2:46 ` Rich Salz
2023-03-02 1:59 Noel Chiappa
2023-03-02 2:11 ` Dan Cross
2023-03-03 18:22 Noel Chiappa
2023-03-03 19:25 ` Chet Ramey
2023-03-03 21:26 ` John Cowan
2023-03-04 0:23 ` Chet Ramey
2023-03-03 19:35 ` Clem Cole
2023-03-04 2:45 ` Jonathan Gray
2023-03-03 23:00 ` Jonathan Gray
2023-03-04 9:07 ` Jonathan Gray
2023-03-04 11:19 ` KenUnix
2023-03-04 14:41 Noel Chiappa
2023-03-04 14:49 ` KenUnix
2023-03-06 8:14 Noel Chiappa
2023-03-06 8:58 ` Jonathan Gray
2023-03-07 2:05 ` Kenneth Goodwin
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=Y/+D3c5Q8tXfVf0L@mit.edu \
--to=tytso@mit.edu \
--cc=jnc@mercury.lcs.mit.edu \
--cc=tuhs@tuhs.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;
as well as URLs for NNTP newsgroup(s).