02-25-2014 10:46 AM
mount -v
/dev/vx/dsk/bootdg/usr on /usr type ufs read-only/setuid/intr/largefiles/onerror=panic/dev=478b3b0
Solved! Go to Solution.
02-26-2014 12:11 AM
If fsck runs clear, try to remount as follows:
mount -F ufs -o rw,remount /usr
02-26-2014 06:09 AM
Hi,
1. Can I run this mount without the Solaris boot disk? My doubt is if I can remount a file system (/usr) where the commands are located.
>> Logically yes, my recommendation here (if possible) would be to bring system to single user mode, unencapsulate. boot via cd or other method & run full fsck on slices. If fsck founds it clean, ensure system boots up in unencapsulated mode, encapsulate again. This is a lenghty way to tackle this problem but would be consistent, this will find the errors & fix the problem. You can alternatively attempt a remount but if there are issues at disk layer, this issue may reoccur.
2. The fsck would be an fsck -F ufs /usr ?
>> yes, first attempt a fsck -F ufs -n <raw device>, this will tell you what errors are available but won't make any changes to filesystem. If the changes are minimal & FS is in recoverable position, you can replace -n with -y switch & re run fsck.
3. There is a way to verify why this file system changed to read only?
>> you will need to refer to system logs, most likely reason is IO errors on filesystem. Try to look through messages file & find if there are any disk/IO related errors.
G
02-26-2014 12:11 AM
If fsck runs clear, try to remount as follows:
mount -F ufs -o rw,remount /usr
02-26-2014 05:46 AM
Hello Marianne,
I have the following questions:
1. Can I run this mount without the Solaris boot disk? My doubt is if I can remount a file system (/usr) where the commands are located.
2. The fsck would be an fsck -F ufs /usr ?
3. There is a way to verify why this file system changed to read only?
Thanks for you help. I'm new with the Veritas Volume Manager.
02-26-2014 06:09 AM
Hi,
1. Can I run this mount without the Solaris boot disk? My doubt is if I can remount a file system (/usr) where the commands are located.
>> Logically yes, my recommendation here (if possible) would be to bring system to single user mode, unencapsulate. boot via cd or other method & run full fsck on slices. If fsck founds it clean, ensure system boots up in unencapsulated mode, encapsulate again. This is a lenghty way to tackle this problem but would be consistent, this will find the errors & fix the problem. You can alternatively attempt a remount but if there are issues at disk layer, this issue may reoccur.
2. The fsck would be an fsck -F ufs /usr ?
>> yes, first attempt a fsck -F ufs -n <raw device>, this will tell you what errors are available but won't make any changes to filesystem. If the changes are minimal & FS is in recoverable position, you can replace -n with -y switch & re run fsck.
3. There is a way to verify why this file system changed to read only?
>> you will need to refer to system logs, most likely reason is IO errors on filesystem. Try to look through messages file & find if there are any disk/IO related errors.
G
02-27-2014 11:43 AM
The issue was fixed with the fsck -F ufs /usr. Thanks for your help.