New answers tagged fsck
The reason you are in read-only mode is that: a) Your file system was found to be damaged, then b) Your OS tried to fix it at boot, but failed, so c) Dropped you into a read-only shell so that you can extract and backup your files without modifying original file system hence preventing you from damaging it further. If I were you, I would try to fix the ...
First, take a look at the Bad Block HOWTO for smartmontools: http://smartmontools.sourceforge.net/badblockhowto.html Second, if you don't already have it, time to implement a working backup strategy. If you need a certain availability of your server, you might also want to consider implementing a RAID-1, mirroring. And either way it's time to get rid ...
In relation to the troubleshooting process, when trying lsof or fuser, don't only check against the relevant partition - check against the disk directly. This quickly would have directed you to the correct solution: Bad: fuser /dev/cciss/c0d0p1 Good: fuser /dev/cciss/c0d0 Bad: lsof /dev/c0d0p1 Good: lsof /dev/ | grep c0d0
Top 50 recent answers are included