Re: Lino SCSI No Show
Re: Lino SCSI No Show
- Subject: Re: Lino SCSI No Show
- From: "Dennis W. Manasco" <email@hidden>
- Date: Mon, 13 Jan 2003 04:22:38 -0600
At 9:16 am -0600 1/12/03, Anthony Sanna wrote:
>fsck -y checks and repairs your filesystem.
I was beginning to X my son's TiPB yesterday, and things got a
little flaky on the OSX partition. I ran Repair Permissions first,
which produced a fairly sizable list fixed files. After that, I ran
DiskWarrior, which also found a list of problems with the newly
installed system.
Are either of these two functions similar to fsck -y, or better
accomplished with this terminal command?
Tony --
fsck and DiskWarrior accomplish similar things, but I don't believe
they are quite identical. Repairing permissions is a completely
different sort of operation.
DiskWarrior is the acknowledged champion at correcting subtle
problems with directory structures, including compaction of
structures to make them smaller and more reliable. AFAIK no other
disk utility goes to the lengths that DiskWarrior does to correct and
optimize minor details of the catalog system; details that most
ignore as irrelevant but DW's authors claim can lead to future
problems. Who's right? I don't know, but DW is an important part of
my toolbox.
I don't know that fsck goes as far into the catalog structure as DW
and I don't believe it does as thorough a job, but I like to use it
because I figure Apple knows more about the eccentricities of their
drivers and file systems than anyone else. A few things I may have
forgotten to mention about fsck: Always use it from single-user mode
(start up with command-s). If fsck finds any problems run it again
(and again) until it finds no problems. (I read somewhere that you
should reboot after fsck finds and corrects problems and _then_ run
it again, but I do not do so. That doesn't mean you shouldn't :)
I would always run fsck first, then DW, then repair permissions.
Repairing permissions does not correct basic problems with the
structure of files or catalogs on you hard disk. Instead it returns
the read/write/access/etc. permissions of important system files and
directories to their "factory" state. This is important because
installations (and certain programs and extensions) may change these
permissions. Some processes depend on them being in their original
state and incorrect permissions can cause them to display
unpredictable behavior, including file corruption.
I wish there was a program, that I trusted, that went the extra step
of checking the integrity of individual files and their catalog
representation in OS X. If there was one I would run it after the
'repair permissions' step above, and probably go through the entire
sequence an additional time just to be sure. Candidates would include
Norton Utilities and Tech Tool Pro/Drive 10. If any of them were
working properly they could fix more subtle problems with individual
files than the above three steps.
Unfortunately I don't yet trust any of them with my OS X disks. That
may well be a mistaken opinion and your mileage may vary. If you do
use them I would strongly caution against issuing a repair
confirmation for a volume with 0 byte content size. (Ouch!)
Best wishes,
-=-Dennis
_______________________________________________
colorsync-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/colorsync-users
Do not post admin requests to the list. They will be ignored.