Let me see if I can find my notebook from that class. It's been a few years.
On Thu, Oct 3, 2013 at 11:04 AM, Yves Dorfsman <[email protected]> wrote: > > Any documentation on this? > Some of us can't make it to those conferences. > > > On 2013-10-03 08:54, Matt Simmons wrote: > >> I was in Ted Ts'o's "Recovering from Linux Hard Drive Disasters" >> (https://www.usenix.org/**conference/lisa13/training-** >> program/full-training-program#**T4<https://www.usenix.org/conference/lisa13/training-program/full-training-program#T4> >> ) >> at LISA one year. Watching him recover data from a crashed fs is a >> thing of >> beauty. >> >> You CAN do amazing things. I'd really recommend that class if you're >> going to >> LISA. >> >> --Matt >> >> >> >> On Thu, Oct 3, 2013 at 10:52 AM, David Lang <[email protected] >> <mailto:[email protected]>> wrote: >> >> In practice, you need to be quite an expert to do anything other than >> -y, >> and even then you will probably only do so if the disk has data on it >> that >> you cannot recover any other way. >> >> for just about any production situation, you would want to build a new >> system or restore from replica/backup instead of doing a manual fsck, >> but >> that assumes that you _have_ the backup and can correctly recreate the >> server, which should be the case, but sometimes isn't ;-p >> >> David Lang >> >> >> On Thu, 3 Oct 2013, Kevin Sandy wrote: >> >> We recently had some issues with one of our filers that wreaked >> all kinds >> of havoc on our systems. Many had to be rebooted to recover from >> read-only >> root filesystems, and quite a few of those needed a manual fsck. >> Which led >> me to wonder: >> >> When faced with filesystem inconsistencies at boot, does anyone do >> anything >> other than just 'fsck -y' on the device? I've never known anyone >> to do >> anything else, but I would have to assume some do, otherwise >> wouldn't >> it be >> automatic? >> >> -- kevin >> >> >> ______________________________**_________________ >> Discuss mailing list >> [email protected] >> <mailto:[email protected].**org<[email protected]> >> > >> >> >> https://lists.lopsa.org/cgi-**bin/mailman/listinfo/discuss<https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss> >> This list provided by the League of Professional System Administrators >> http://lopsa.org/ >> >> ______________________________**_________________ >> Discuss mailing list >> [email protected] >> <mailto:[email protected].**org<[email protected]> >> > >> >> >> https://lists.lopsa.org/cgi-**bin/mailman/listinfo/discuss<https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss> >> This list provided by the League of Professional System Administrators >> http://lopsa.org/ >> >> >> >> >> -- >> LITTLE GIRL: But which cookie will you eat FIRST? >> COOKIE MONSTER: Me think you have misconception of cookie-eating process. >> >> >> ______________________________**_________________ >> Discuss mailing list >> [email protected] >> https://lists.lopsa.org/cgi-**bin/mailman/listinfo/discuss<https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss> >> This list provided by the League of Professional System Administrators >> http://lopsa.org/ >> >> > > -- > Yves. > http://www.SollerS.ca/ > Unix/Linux and Python specialist in > Calgary. > > http://blog.zioup.org/ > > ______________________________**_________________ > Discuss mailing list > [email protected] > https://lists.lopsa.org/cgi-**bin/mailman/listinfo/discuss<https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss> > This list provided by the League of Professional System Administrators > http://lopsa.org/ > -- LITTLE GIRL: But which cookie will you eat FIRST? COOKIE MONSTER: Me think you have misconception of cookie-eating process.
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
