From: Rob Pike <robpike@gmail.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: The Unix Heretics Society mailing list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Is it time to resurrect the original dsw (delete with switches)?
Date: Mon, 30 Aug 2021 11:21:29 +1000 [thread overview]
Message-ID: <CAKzdPgyoL1qKZCvk2CJ3zZvJKpVccVkVOYUkwuTLO54J7Uyb5g@mail.gmail.com> (raw)
In-Reply-To: <20210829235745.GC20021@mcvoy.com>
[-- Attachment #1: Type: text/plain, Size: 1968 bytes --]
Do you even have input switches and HALT/CONT switches? I don't think so....
Commiserations.
-rob
On Mon, Aug 30, 2021 at 9:58 AM Larry McVoy <lm@mcvoy.com> wrote:
> On Sun, Aug 29, 2021 at 03:12:16PM -0700, Jon Steinhart wrote:
> > After a bit of poking around I discovered that btrfs SILENTLY remounted
> the
> > filesystem because it had errors. Sure, it put something in a log file,
> > but I don't spend all day surfing logs for things that shouldn't be going
> > wrong. Maybe my expectation that filesystems just work is antiquated.
>
> I give them credit for remounting read-only when seeing errors, they may
> have gotten that from BitKeeper. When we opened a history file, if we
> encountered any errors we opened the history file in read only mode so
> if it worked enough you could see your data, great, but don't write on
> top of bad data.
>
> > Although it's been discredited by some, I'm still a believer in "stop and
> > fsck" policing of disk drives.
>
> Me too. Though with a 32TB drive (I'm guessing rotating media), that's
> going to take a long time. If I had a drive that big, I'd divide it
> into managable chunks and mount them all under /drive/{a,b,c,d,e...}
> so that when something goes wrong you don't have to check the whole
> 32TB.
>
> > Near the top of the manual page it says:
> >
> > Warning
> > Do not use --repair unless you are advised to do so by a developer
> > or an experienced user, and then only after having accepted that
> > no fsck successfully repair all types of filesystem corruption. Eg.
> > some other software or hardware bugs can fatally damage a volume.
> >
> > Whoa! I'm sure that operators are standing by, call 1-800-FIX-BTRFS.
> > Really? Is a ploy by the developers to form a support business?
>
> That's a stretch, they are just trying to not encourage you to make a
> mess.
>
> I sent Linus an email to find out where btrfs is, I'll report back when
> he replies.
>
> --lm
>
[-- Attachment #2: Type: text/html, Size: 2594 bytes --]
next prev parent reply other threads:[~2021-08-30 1:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 22:12 Jon Steinhart
2021-08-29 23:09 ` Henry Bent
2021-08-30 3:14 ` Theodore Ts'o
2021-08-30 13:55 ` Steffen Nurpmeso
2021-08-30 9:14 ` John Dow via TUHS
2021-08-29 23:57 ` Larry McVoy
2021-08-30 1:21 ` Rob Pike [this message]
2021-08-30 3:46 ` Theodore Ts'o
2021-08-30 23:04 ` Bakul Shah
2021-09-02 15:52 ` Jon Steinhart
2021-09-02 16:57 ` Theodore Ts'o
2021-08-30 3:36 ` Bakul Shah
2021-08-30 11:56 ` Theodore Ts'o
2021-08-30 22:35 ` Bakul Shah
2021-08-30 15:05 ` Steffen Nurpmeso
2021-08-31 13:18 ` Steffen Nurpmeso
2021-08-30 21:38 ` Larry McVoy
2021-08-30 13:06 Norman Wilson
2021-08-30 14:42 ` Theodore Ts'o
2021-08-30 18:08 ` Adam Thornton
2021-08-30 16:46 ` Arthur Krewat
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=CAKzdPgyoL1qKZCvk2CJ3zZvJKpVccVkVOYUkwuTLO54J7Uyb5g@mail.gmail.com \
--to=robpike@gmail.com \
--cc=lm@mcvoy.com \
--cc=tuhs@minnie.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).