From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 22744 invoked from network); 29 Aug 2021 23:58:15 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 29 Aug 2021 23:58:15 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 75A419D52F; Mon, 30 Aug 2021 09:58:11 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 32A899D52C; Mon, 30 Aug 2021 09:57:50 +1000 (AEST) Received: by minnie.tuhs.org (Postfix, from userid 112) id 74CA09D52B; Mon, 30 Aug 2021 09:57:47 +1000 (AEST) Received: from mcvoy.com (mcvoy.com [192.169.23.250]) by minnie.tuhs.org (Postfix) with ESMTPS id 8647F9D52A for ; Mon, 30 Aug 2021 09:57:46 +1000 (AEST) Received: by mcvoy.com (Postfix, from userid 3546) id F2F3035E123; Sun, 29 Aug 2021 16:57:45 -0700 (PDT) Date: Sun, 29 Aug 2021 16:57:45 -0700 From: Larry McVoy To: Jon Steinhart Message-ID: <20210829235745.GC20021@mcvoy.com> References: <202108292212.17TMCGow1448973@darkstar.fourwinds.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202108292212.17TMCGow1448973@darkstar.fourwinds.com> User-Agent: Mutt/1.5.24 (2015-08-30) Subject: Re: [TUHS] Is it time to resurrect the original dsw (delete with switches)? X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: The Unix Heretics Society mailing list Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" 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