Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I would like to know the names of files affected by fsck.ext3 .
It seems like this is an important feature entirely missing from fsck.
Currently, the only information fsck shows is block numbers and inode numbers.
Is there a way to find out file names affected by an fsck repair (specifically fsck.ext3)?
Is there a different program that can lookup block numbers to file names?
fsck has a number of options. See man fsck for the full details, but perhaps you need to use the -V option, and maybe tee or redirect the output to a logfile.
If you have already run fsck without these options, the repairs will have already been made, as best fsck can (and it's pretty robust in my experience).
I looked at command line options in 'man fsck' and 'man fsck.ext3'.
I have tested the verbose option. -v (lowercase) for verbose, does not print any file name information.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.