My internal partition which has read write permission earlier,
turned back to readonly mode.
Note : before running fsck, advised to get an idea
Distributed Hadoop cluster setup Issue while setup Hadoop cluster
turned back to readonly mode.
issue
when I tried to change it into full permission by
root@boss[bin]# sudo chmod 777 -R /media/bdtools
, I got chmod changing permissions of read-only file system
root@boss[bin]# sudo chmod 777 -R /media/bdtools
, I got chmod changing permissions of read-only file system
Then i tried to re-mount the partition, as many people were discussed over web.
root@boss[bin]# mount -o remount,rw /dev/sda9 /media/bdalab/bdtools
, I got filesystem drive is now write-protected
root@boss[bin]# mount -o remount,rw /dev/sda9 /media/bdalab/bdtools
, I got filesystem drive is now write-protected
Solution
I have gone through the dmesg log, have seen error like
ext4_put_super:792: Couldn't clean up the journal
I followd below approach to overcome the readonly filesystem issue.
I have gone through the dmesg log, have seen error like
ext4_put_super:792: Couldn't clean up the journal
I followd below approach to overcome the readonly filesystem issue.
1) un mount the partition
2) fsck /dev/sda9
3) remount the partition
2) fsck /dev/sda9
3) remount the partition
Note : before running fsck, advised to get an idea
posts you may like
solution for Hadoop High AvailabilityDistributed Hadoop cluster setup Issue while setup Hadoop cluster
2 comments:
this code fucked me. i unmonted my partition and now its not mounting again...................
Really appreciate the clarity and structure of this post, it was easy to follow. While exploring reaction time test, I noticed how response speed and reflex improvement play a big role in handling system-level timing issues.
Post a Comment