위키
포럼
도구
바뀐글
랜덤

리눅스 Read-only file system

Question mark2.svg 해결되지 않은 문제입니다.
Read-only file system
mount: block device is write-protected, mounting read-only

1 예시[ | ]

Console
Copy
[root@zetawiki ~]# cat /etc/fstab
/dev/VolGroup00/LogVol00 /                       ext3    defaults        1 1
LABEL=/boot             /boot                   ext3    defaults        1 2
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
/dev/VolGroup00/LogVol01 swap                    swap    defaults        0 0
Console
Copy
[root@zetawiki ~]# cat /etc/mtab
/dev/mapper/VolGroup00-LogVol00 / ext3 rw 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
/dev/vda1 /boot ext3 rw 0 0
tmpfs /dev/shm tmpfs rw 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
Console
Copy
[root@zetawiki ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                       35G  7.9G   26G  24% /
/dev/vda1              99M   27M   68M  28% /boot
tmpfs                1006M     0 1006M   0% /dev/shm
Console
Copy
[root@zetawiki ~]# touch a
touch: setting times of `a': Read-only file system
Console
Copy
[root@zetawiki ~]# touch /boot/a
[root@zetawiki ~]# rm -f /boot/a
Console
Copy
[root@zetawiki ~]# fsck
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
/dev/VolGroup00/LogVol00: recovering journal
Clearing orphaned inode 1962250 (uid=0, gid=0, mode=0100600, size=130)
Clearing orphaned inode 1962247 (uid=27, gid=27, mode=0100600, size=0)
Clearing orphaned inode 1962246 (uid=27, gid=27, mode=0100600, size=0)
Clearing orphaned inode 1962245 (uid=27, gid=27, mode=0100600, size=0)
Clearing orphaned inode 1962244 (uid=27, gid=27, mode=0100600, size=0)
Clearing orphaned inode 1962243 (uid=27, gid=27, mode=0100600, size=0)
/dev/VolGroup00/LogVol00: clean, 140202/9451456 files, 2342044/9445376 blocks
e2fsck 1.39 (29-May-2006)
/dev/vda1 is mounted.  
 
WARNING!!!  Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
 
Do you really want to continue (y/n)? yes
 
/boot: recovering journal
/boot: clean, 47/26104 files, 30099/104388 blocks
Console
Copy
[root@zetawiki ~]# fsck
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
/dev/VolGroup00/LogVol00: clean, 140202/9451456 files, 2342044/9445376 blocks
e2fsck 1.39 (29-May-2006)
/dev/vda1 is mounted.  

WARNING!!!  Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? yes

/boot: clean, 47/26104 files, 30099/104388 blocks
Console
Copy
[root@zetawiki ~]# mount -a
[root@zetawiki ~]# touch a
touch: setting times of `a': Read-only file system
Console
Copy
[root@zetawiki ~]# mount -n -o remount,rw /
mount: block device /dev/VolGroup00/LogVol00 is write-protected, mounting read-only
Console
Copy
[root@zetawiki ~]# mount -o remount,rw /
mount: block device /dev/VolGroup00/LogVol00 is write-protected, mounting read-only
Console
Copy
[root@zetawiki ~]# cat /etc/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
#          initrd /initrd-version.img
#boot=/dev/vda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-348.16.1.el5)
	root (hd0,0)
	kernel /vmlinuz-2.6.18-348.16.1.el5 ro root=/dev/VolGroup00/LogVol00
	initrd /initrd-2.6.18-348.16.1.el5.img
title CentOS (2.6.18-308.4.1.el5)
	root (hd0,0)
	kernel /vmlinuz-2.6.18-308.4.1.el5 ro root=/dev/VolGroup00/LogVol00
	initrd /initrd-2.6.18-308.4.1.el5.img
title CentOS (2.6.18-238.el5)
	root (hd0,0)
	kernel /vmlinuz-2.6.18-238.el5 ro root=/dev/VolGroup00/LogVol00
	initrd /initrd-2.6.18-238.el5.img
Console
Copy
[root@zetawiki ~]# fsck /dev/VolGroup00/LogVol00
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
/dev/VolGroup00/LogVol00: clean, 140202/9451456 files, 2342044/9445376 blocks
Console
Copy
[root@zetawiki ~]# dmesg | grep -i ext3
sizeof(ext3inode)=760 bytes
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
EXT3-fs: dm-0: orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 2523468
ext3_orphan_cleanup: deleting unreferenced inode 7326005
ext3_orphan_cleanup: deleting unreferenced inode 1962247
ext3_orphan_cleanup: deleting unreferenced inode 1962246
ext3_orphan_cleanup: deleting unreferenced inode 1962245
ext3_orphan_cleanup: deleting unreferenced inode 1962244
ext3_orphan_cleanup: deleting unreferenced inode 1962243
EXT3-fs: dm-0: 7 orphan inodes deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
EXT3 FS on dm-0, internal journal
EXT3 FS on vda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-fs error (device dm-0): ext3_lookup: unlinked inode 6835814 in dir #5593510
ext3_abort called.
EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal
EXT3-fs error (device dm-0): ext3_lookup: unlinked inode 6835831 in dir #5690542
ext3_abort called.
EXT3-fs error (device dm-0): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device dm-0): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device dm-0): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs error (device dm-0): ext3_remount: Abort forced by user

2 같이 보기[ | ]

원본 주소 "https://zetawiki.com/w/index.php?title=리눅스_Read-only_file_system&oldid=604756"