| To: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: Lost+found |
| From: | Emmanuel Florac <eflorac@xxxxxxxxxxxxxx> |
| Date: | Thu, 10 Apr 2008 10:51:20 +0200 |
| Cc: | Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>, Barry Naujok <bnaujok@xxxxxxx>, Jeffrey Sandel <webmaster@xxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <47FCC071.40201@sandeen.net> |
| Organization: | Intellique |
| References: | <1207632033.11530.10.camel@localhost.localdomain> <op.t9bm23aa3jf8g2@pc-bnaujok.melbourne.sgi.com> <alpine.DEB.1.10.0804090628080.322@p34.internal.lan> <47FCC071.40201@sandeen.net> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
Le Wed, 09 Apr 2008 08:11:13 -0500 Eric Sandeen <sandeen@xxxxxxxxxxx> écrivait: > Crosses my mind that one could probably write a generic tool which > could work with a package manager db to check file md5sums > in /lost+found, if the files happen to be system files installed via > a package.... Yup, I've done something similar when I used a PC with a bugged via chipset which regularly broke apart filesystems under heavy load... I used a tool named afick to index the whole disks (it stores md5 of everything in a small db) and with some tinkering I was able to restore everything from lost+found each time some filesystem went belly up (once a month...) -- ---------------------------------------- Emmanuel Florac | Intellique ---------------------------------------- |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [GIT PULL] XFS update for 2.6.25-rc9, Lachlan McIlroy |
|---|---|
| Next by Date: | TAKE 980084 - Ensure the inode is joined in xfs_itruncate_finish, David Chinner |
| Previous by Thread: | Re: Lost+found, Niv Sardi |
| Next by Thread: | [REVIEW #2] cleanup - remove bhv_vname_t, Barry Naujok |
| Indexes: | [Date] [Thread] [Top] [All Lists] |