I don't know offhand if fsck will actually look for fid files which
don't have any rows in the 'file' table. Well, I'm pretty confident it
doesn't. If you end up with three rows in file_on that's what it'll look
for. It won't do a desperate search across all of the devices unless
it's lost a file's data entirely.
-Dormando
Jared Klett wrote:
I believe 'mogadm fsck' should take care of this. Dormando or Mark,
feel free to correct me.
On our MogileFS cluster, I run 'mogadm fsck start' at 2 AM and 'mogadm
fsck stop' at 7 AM, via cron. So far, it's found a good number of quirks (and
fixed them, I assume) from looking at the log ('mogadm fsck printlog').
I'd be interested to hear how other people are using fsck and what
their results are.
cheers,
- Jared
