ive tried this; zimbra@zimbra:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1
UUID=84444b1a-2a71-42f3-9136-f0a142656422 / ext3 relatime,errors=remount-ro 0
# /dev/sda5
UUID=67867243-51ea-4fd6-ac11-20af92c5fa07 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
================================================== ========
result; zimbra@zimbra:~$ sudo e2fsck -C0 -p -f -v /dev/sda1
sudo: unable to resolve host zimbra
[sudo] password for zimbra:
Duplicate or bad block in use!
/dev/sda1: Multiply-claimed block(s) in inode 4440762: 17768834
/dev/sda1: Multiply-claimed block(s) in inode 4440777: 17768834
/dev/sda1: (There are 2 inodes containing multiply-claimed blocks.)
/dev/sda1: File /opt/zimbra/log/zmlogprocess.pid (inode #4440762, mod time Sun Jun 7 20:10:02 20 09)
has 1 multiply-claimed block(s), shared with 1 file(s):
/dev/sda1: /opt/zimbra/log/.zmcontrol.cache (inode #4440777, mod time Sun Jun 7 20:20:03 20 09)
/dev/sda1:
/dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
zimbra@zimbra:~$
--------------------------------------------------------------------------
is it safe? how much is the risk of getting the /opt corrupted or messed up if i run sudo e2fsck -f -y -v /dev/sda1?
what's the better alternative? |