Tag Info

Hot answers tagged

4

Do not attempt to mount directly the device ! You need to mount a partition of it. For example, this is wrong when you do: mount /dev/sda /mnt What you should do is: mount /dev/sda3 /mnt The system need the meta-data enclosed in the partition to know what to do with it. If you mount directly the device, these meta-data are missing and the mount will ...


2

The order of reboots is important. Rebooting the server after the clients can result in this situation. The stale NFS handle indicates that the client has a file open, but the server no longer recognizes the file handle. In some cases, NFS will cleanuo its data structures after a timeout. In other cases, you will need to clean the NFS data structures ...


1

When using mount you have to mount the partition not the drive itself eg mount -t ext4 /dev/sda1 /data


1

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


1

You should check the cron files for whatever is inside /etc/cron* and if any "sudoed" users got a cron inside /var/spool/cron/crontabs/ that could umount something. autofs can also do stupide stuff with mount binds, but I've never seen it happen.



Only top voted, non community-wiki answers of a minimum length are eligible