From: milov@cs.uwlax.edu (Milo Velimirovic)
Subject: [TUHS] shutdown for pre-v7 unix
Date: Thu, 17 Jul 2014 21:58:00 -0500 [thread overview]
Message-ID: <A4FCD121-EF38-45B9-8943-7C738204C17F@cs.uwlax.edu> (raw)
In-Reply-To: <CAGSRWbjWcm3oX9qhKJvA0V88J_L2J1B_kq9fFmS9a1dah7Tmvw@mail.gmail.com>
Three <mumble> for the Elven-kings under the sky,
On Jul 17, 2014, at 9:52 PM, Tim Newsham wrote:
> One sync for the disks and two for the operator's peace of mind...
>
> On Thu, Jul 17, 2014 at 4:26 PM, Ronald Natalie <ron at ronnatalie.com> wrote:
>>
>> On Jul 17, 2014, at 4:16 PM, Clem Cole <clemc at ccc.com> wrote:
>>
>> I think that's is a problem in that it needs to be data blocks, inodes, and
>> finally superblocks to do the least damage in a crash.
>>
>>
>> That is definitely the case and that was perhaps the biggest fix in BSD (and
>> other later) was to make the file system writing more consistent so at least
>> you didn't get trashed filesystems but at worst got some orphaned blocks
>> that needed intervention to reclaim.
>>
>> It was mandatory for operators at JHU to understand how the file system was
>> laid out on disk, and what icheck/dcheck reported and what the options to
>> fix things. Link counts that were too low and dups in free should NEVER
>> happen with an intelligently ordered set of I/O operations, but thats not
>> what Version 6 UNIX had. It wasn't uncommon to find several errors in the
>> file system that would be degenerate system faults if not corrected.
>>
>> But all that aside, even in those shakey days, typing sync multiple times
>> really didn't accomplish anything and it because less useful as the file
>> systems became more stable.
>>
>>
>>
>> _______________________________________________
>> TUHS mailing list
>> TUHS at minnie.tuhs.org
>> https://minnie.tuhs.org/mailman/listinfo/tuhs
>>
>
>
>
> --
> Tim Newsham | www.thenewsh.com/~newsham | @newshtwit | thenewsh.blogspot.com
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
next prev parent reply other threads:[~2014-07-18 2:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 18:55 Mark Longridge
2014-07-16 20:52 ` Brantley Coile
2014-07-17 2:29 ` Win Treese
2014-07-16 21:12 ` Dave Horsfall
2014-07-16 21:23 ` Dave Horsfall
2014-07-17 2:09 ` Dan Stromberg
2014-07-17 15:58 ` Warner Losh
2014-07-17 16:15 ` Clem Cole
2014-07-17 18:04 ` Ronald Natalie
2014-07-17 20:16 ` Clem Cole
2014-07-18 2:26 ` Ronald Natalie
2014-07-18 2:52 ` Tim Newsham
2014-07-18 2:58 ` Milo Velimirovic [this message]
2014-07-18 3:42 ` Warner Losh
2014-07-16 19:47 Noel Chiappa
2014-07-17 2:40 Norman Wilson
2014-07-17 3:55 Noel Chiappa
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=A4FCD121-EF38-45B9-8943-7C738204C17F@cs.uwlax.edu \
--to=milov@cs.uwlax.edu \
/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).