mklost+found on 209GB lvol

[Joe Profaizer]

This command has been running for over an hour. Is this normal on this big of logical volume? I noticed there is a tee process (tee 11 12 13 14 15 16 17 18) running also. I was unable to kill -9 this process. Currently, I can't run a bdf, ll, or other related commands.

..Joe

[harry d brown jr]

Did you just create this LV? When you say you can't run bdf or ll, does that mean anywhere, like in the / directory (bdf / or ll /)?

[Patrick Wallek]

If bdf, ll, etc. hang and you can't break them and can't kill them, then they are waiting on I/O and won't finish until they get it. I wouldn't think that mklost+found should take that long to run. Are all of your disks in that particular LV OK? You don't have a bad disk anywhere on a non-mirrored non-raid5'd LV do you? Or any other kind of problem that would cause you not to be able to see any or all of an LV? Anything like that would definitely cause the types of problems you are seeing.

[Joe Profaizer]

All disks are just fine. lvdisplay comes back normal. I don't see anything out of the norm. Should I just reboot?

[James R. Ferguson]

Hi Joe:

Did you kill a pfs_mount perchance? Doing this would yield the symptoms you descibe including high CPU utilization. If this is the case, bite the bullet and reboot; you have not other recourse.

Regards!

...JRF...

[Joe Profaizer]

Nothing to do w/ pfs_mount, although I have been bitten by that before.