To se rešava restartom.
Međutim, zašto se to uopšte dešava? Ako je hardverski problem (disk na samrti), zašto se posle restarta sve vrati na normalu?
root@etis:/# mkdir proba
mkdir: cannot create directory `proba': Read-only file system
root@etis:/# df -h
-bash: /usr/bin/df: Input/output error
root@etis:~# mount
/dev/sda1 on / type reiserfs (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
root@etis:/etc# ls -lh
ls: cannot access imrc: Permission denied
ls: cannot access mutt: Permission denied
ls: cannot access skel: Permission denied
ls: cannot access dialogrc: Permission denied
ls: cannot access minirc.dfl: Permission denied
ls: cannot access esd.conf: Permission denied
ls: cannot access my-small.cnf: Permission denied
ls: cannot access radiusclient: Permission denied
ls: cannot access htdig: Permission denied
ls: cannot access rc0.d: Permission denied
ls: cannot access rc1.d: Permission denied
ls: cannot access rc3.d: Permission denied
...
-rw-r--r-- 1 root root 36 2008-11-03 15:48 organization
-rw-r--r-- 1 root root 1.3K 2012-08-04 13:34 passwd
?????????? ? ? ? ? ? passwd-
?????????? ? ? ? ? ? passwd.new
-rw-r--r-- 1 root root 889 2008-11-03 15:48 pear.conf
-rw-r--r-- 1 root root 18K 2008-11-03 15:48 pine.conf
-rw-r--r-- 1 root root 214 2012-08-04 16:20 printcap
-rw-r--r-- 1 root root 2.4K 2010-07-25 23:24 profile
?????????? ? ? ? ? ? profile.new
-rw-r--r-- 1 root root 2.1K 2008-11-03 15:48 proftpd.conf
-rw-r--r-- 1 root root 5.7K 2008-11-03 15:48 protocols
?????????? ? ? ? ? ? radiusclient
-rw------- 1 root root 4.0K 2012-08-04 16:19 random-seed
-rw------- 1 root root 1018 2009-02-03 20:31 rarfiles.lst
?????????? ? ? ? ? ? rc.d_bekap111213
?????????? ? ? ? ? ? rc0.d
?????????? ? ? ? ? ? rc1.d
lrwxrwxrwx 1 root root 10 2009-01-25 03:46 rc2.d -> rc.d/rc2.d/
?????????? ? ? ? ? ? rc3.d
lrwxrwxrwx 1 root root 10 2009-01-25 03:46 rc4.d -> rc.d/rc4.d/
lrwxrwxrwx 1 root root 10 2009-01-25 03:46 rc5.d -> rc.d/rc5.d/
lrwxrwxrwx 1 root root 10 2009-01-25 03:46 rc6.d -> rc.d/rc6.d/
-rw-r--r-- 1 root root 160 2012-07-25 18:24 resolv.conf
lrwxrwxrwx 1 root root 16 2009-01-25 03:46 rmt -> /usr/libexec/rmt
-rw-r--r-- 1 root root 1.2K 2012-03-15 10:17 rndc.conf
...
root@etis:/etc# fsck.reiserfs /dev/sda1
reiserfsck 3.6.19 (2003 www.namesys.com)
*************************************************************
** If you are using the latest reiserfsprogs and it fails **
** please email bug reports to [email protected], **
** providing as much information as possible -- your **
** hardware, kernel, patches, settings, all reiserfsck **
** messages (including version), the reiserfsck logfile, **
** check the syslog file for any related information. **
** If you would like advice on using this program, support **
** is available for $25 at www.namesys.com/support.html. **
*************************************************************
Will read-only check consistency of the filesystem on /dev/sda1
Will put log info to 'stdout'
Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
The problem has occurred looks like a hardware problem. If you have
bad blocks, we advise you to get a new hard drive, because once you
get one bad block that the disk drive internals cannot hide from
your sight,the chances of getting more are generally said to become
much higher (precise statistics are unknown to us), and this disk
drive is probably not expensive enough for you to you to risk your
time and data on it. If you don't want to follow that follow that
advice then if you have just a few bad blocks, try writing to the
bad blocks and see if the drive remaps the bad blocks (that means
it takes a block it has in reserve and allocates it for use for
of that block number). If it cannot remap the block, use badblock
option (-B) with reiserfs utils to handle this block correctly.
bread: Cannot read the block (2622591): (Input/output error).
Aborted