Messages in this thread | | | Subject | Re: Removing bad fsck inode files | Date | Wed, 03 Nov 1999 01:05:14 -0300 | From | Horst von Brand <> |
| |
"Tom Livingston" <tsl@volition.org> said:
[...]
> However, during the fsck process I got a large number of files in > lost+found. No surprise there, but many of them are corrupted enough not to > be removable. As it stands now I have 13,000 files in lost+found that I > can't rm as root, or chown, or chmod.
Do a:
ls lost+found | sed -e 's;^;rm ;' > /tmp/to-delete
and then feed that to debugfs(8). A fsck(8) should finish up the mess.
[Warning: Don't try this at home. Professional drivers made the demonstration] -- Horst von Brand vonbrand@sleipnir.valparaiso.cl Casilla 9G, Viña del Mar, Chile +56 32 672616
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |