On Thu, Oct 24, 2013 at 11:27 AM, hari prasadh wrote:
>
> """
> Buffer I/O error on device dm-2, logical block 1309683
> lost page write due to I/O error on dm-2
> Buffer I/O error on device dm-2, logical block 1309684
> lost page write due to I/O error on dm-2
> Buffer I/O error on device dm-2,
On Thu, Oct 24, 2013 at 11:27 AM, hari prasadh wrote:
> Hi All,
>
> Again iam facing the same issues as turned back to read mode.
> please find below dmesg log and these are the lines which is above and
> below the line *"Journal has aborted"*
Run a SMART test on your HDD to ensure it isn't faili
Hi All,
Again iam facing the same issues as turned back to read mode.
please find below dmesg log and these are the lines which is above and
below the line *"Journal has aborted"*
"""
Buffer I/O error on device dm-2, logical block 1309683
lost page write due to I/O error on dm-2
Buffer I/O error
On Wed, Oct 16, 2013 at 10:03 PM, hari prasadh wrote:
> Thanks for your responses.It has 13%usage only while checking with df -h
> and all the necessary permissions present in folder and partition
> level.atthat time i haven't any clues...i have checked for
> /var/log/messages and
> dmesg|less to
Thanks for your responses.It has 13%usage only while checking with df -h
and all the necessary permissions present in folder and partition
level.atthat time i haven't any clues...i have checked for
/var/log/messages and
dmesg|less too.i havent got any clues and iam in short of time to analyse
furt
On Wed, 2013-10-16 at 11:13 +0530, hari prasadh wrote:
> *[sudo] password for XXX:*
> *sudo: unable to open /var/db/sudo/XXX/1: Read-only file system*
It looks like a Harddisk issue. Check if you have 'Journal has aborted'
line in /var/log/messages or 'dmesg' output. If you look at the lines
abov
On Wed, Oct 16, 2013 at 5:17 AM, Shrinivasan T wrote:
> > *[sudo] password for XXX:*
> > *sudo: unable to open /var/db/sudo/XXX/1: Read-only file system*
> > **
> > *
> >
> > touch test.txt
> >
> > touch: cannot touch `test.txt': >Read-only file system
>
> This may due to some error on filesystem.
OK, imagine your root partition is hda2
then try:
mount -o remount,rw /dev/hda2 /
this might help to resolve the issue.
On Wed, Oct 16, 2013 at 11:33 AM, Noorul Islam Kamal Malmiyoda <
noo...@noorul.com> wrote:
> On Oct 16, 2013 11:13 AM, "hari prasadh" wrote:
> >
> > *Hi All,*
> > **
> > *
> *[sudo] password for XXX:*
> *sudo: unable to open /var/db/sudo/XXX/1: Read-only file system*
> **
> *
>
> touch test.txt
>
> touch: cannot touch `test.txt': >Read-only file system
This may due to some error on filesystem.
Backup all data and recreate filesystem using mkfs utilities.
__
On Wed, Oct 16, 2013 at 1:43 AM, hari prasadh wrote:
> *Hi All,*
> **
> *In my Centos box,till yesterday i was able to create folder/files(able to
> read/write),etc.But from yesterday onwards suddenly the file sytem is
> changed to readonly mode without any interruptions.But from yesterday i was
On Oct 16, 2013 11:13 AM, "hari prasadh" wrote:
>
> *Hi All,*
> **
> *In my Centos box,till yesterday i was able to create folder/files(able to
> read/write),etc.But from yesterday onwards suddenly the file sytem is
> changed to readonly mode without any interruptions.But from yesterday i
was
> n
*Hi All,*
**
*In my Centos box,till yesterday i was able to create folder/files(able to
read/write),etc.But from yesterday onwards suddenly the file sytem is
changed to readonly mode without any interruptions.But from yesterday i was
not able to create folder/files(able to read/write),etc .*
*is
12 matches
Mail list logo
