|
|
File system journaling won't prevent all disk damage
> To check a journalled startup disk you can also restart in single
File system journaling won't prevent all disk damage
>To check a journalled startup disk you can also restart in single user mode (hold down Cmd-S at startup) and then type fsck -y By default, fsck will look at all volumes mentioned in the system's files system table (/etc/fstab according to the manual). You can also specify exactily which file system you want to check from the command line. While there is an arcane variant that works on non-startup volumes, who but students of Unix with upmteen years under their belts will remember the procedure while in single-user mode? Well, I have 10 years experience with Unix and I still can't remember all the options to all of the programs I use - especially fsck[*]. However I do know how to read a the online manual and find out. Fortunately single-user mode still allows you to read the online manual. If you think a GUI is for wimps, there's always Linux. I'm sorry, I missed your point there ..... Douglas [*] fsck is one of those programs that you don't want to have to run manually ;-)
File system journaling won't prevent all disk damage
No! To repeat, ...
File system journaling won't prevent all disk damage
sbin/fsck -fy will repair a journaled startup volume
File system journaling won't prevent all disk damage
After twenty years, I see that TheWormyFruitâ„¢ finally wised-up and its new Xserve G5 |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|