- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Read Only File Systems
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-26-2010 10:18 AM
тАО03-26-2010 10:18 AM
Read Only File Systems
This is the messaged displayed in system log:
Mar 25 18:32:26 dbserver kernel: sd 0:0:0:3: [sdc] Attached SCSI disk
Mar 25 18:32:26 dbserver kernel: sd 0:0:0:3: Attached scsi generic sg9 type 0
Mar 25 18:32:26 dbserver kernel: sd 1:0:0:2: [sdh] Write cache: disabled, read cache: enabled, supports DPO and FUA
Mar 25 18:32:26 dbserver kernel: sd 1:0:0:2: [sdh] 524288000 512-byte hardware sectors: (268 GB/250 GiB)
Mar 25 18:32:26 dbserver kernel: sd 1:0:0:2: [sdh] Write Protect is off
Mar 25 18:32:26 dbserver kernel: sd 1:0:0:2: [sdh] Mode Sense: 97 00 10 08
Mar 25 18:32:26 dbserver kernel: sd 1:0:0:2: [sdh] Write cache: disabled, read cache: enabled, supports DPO and FUA
Multipath software is enabled in all operating systems. Actually, multipath reported a loss in one of the paths and continued accesing the file systems through the remaining active path, but in read-only mode. I consider this is not a normal condition, since I've been working with EVA arrays (but attached to UNIX systems) and I never experienced this kind of scenario.
One interesting remark, the Windows servers didn't suffer any interference on the disks, the OS only reported a loss in one of the path and then acknowledged the restored path.
I would like your help on this issue and tell me what caused this condition. Thanks in advanced.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-26-2010 10:57 AM
тАО03-26-2010 10:57 AM
Re: Read Only File Systems
Are the Linux filesystems in LVM? If so, are the volume groups using the multipath devices or the /dev/sd* devices?
JP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-26-2010 11:32 AM
тАО03-26-2010 11:32 AM
Re: Read Only File Systems
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2010 02:09 PM
тАО03-27-2010 02:09 PM
Re: Read Only File Systems
In Red Hat, when a file system goes read only its because of a bad disk.
Since multipath reported only one active path, I would assume the other has a HW problem. Probably an HBA on the Unix server since none of the windows servers didn't suffer.
I'm guessing that in Suse you'll find HBA status as you would for Red Hat, under /pro/scsi/qla#### for qlogic FC HBA. Let me know if you have Emmulex HBA's or something else.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-28-2010 06:54 PM
тАО03-28-2010 06:54 PM
Re: Read Only File Systems
this include busy I/O retry or SAN path failover errors.
and Redhat suggested to upgrade the kernel.
What kernel you running.
This problem is in most of the LINUX flavours I suppose.
BR,
Kapil+
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-29-2010 01:56 AM
тАО03-29-2010 01:56 AM
Re: Read Only File Systems
When the filesyetem is not confugred properly to be accessed form mor ethan 1 location; there are bound to be issues wherein the file system becomes read only. Make sure that you configure it properly if it is to be used from 2 locations.
Cheers
Vipul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-29-2010 07:48 AM
тАО03-29-2010 07:48 AM
Re: Read Only File Systems
vendor "HP├в
product "HSV2[01]0|HSV300|HSV4[05]0"
getuid_callout ├в /lib/udev/scsi_id -g -u /dev/%n├в
prio_callout alua
hardware_handler "0"
path_selector "round-robin 0"
path_grouping_policy group_by_prio
failback immediate
rr_weight uniform
no_path_retry 18
rr_min_io 100
path_checker tur
As far as I know, when you have multipath implemented, if one the path fails the file systems should continue to be accesible (through the remaining active path), this is one the purpose of multipath, at least this is the case in UNIX environments (HP-UX, Solaris, AIX, etc.).
Once you customize the multipath configuration template, there is nothing else to do in the file systems.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-29-2010 07:54 PM
тАО03-29-2010 07:54 PM
Re: Read Only File Systems
are the windows severs running the mpio product or not? if not, then they are single path to the one eva controller -- which one seems to have the link lights on the ports flashing when database is running ?
maybe a visual view might help. maybe you have lost command-view from seeing the array, so its not just linux..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-30-2010 07:00 AM
тАО03-30-2010 07:00 AM
Re: Read Only File Systems
The Command View problem is, according to some threads in the forum, related to a bug in the controller firmware and it should be solved with and upgrade. I even presented a virtual disk to the Command View server, and it worked, so the problem is not the path or zoning, the problem is just with the Linux servers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-31-2010 01:51 AM
тАО03-31-2010 01:51 AM
Re: Read Only File Systems
here is how we tuned scsiid_config, lvm.conf and multipath.conf, but with EMC Clariion.
~]# cat /etc/scsi_id.config |grep -v '#'
options=-g
vendor="DGC",options=-p 0x83
Also tuned lvm filter and multipath.conf
#cat /etc/lvm/lvm.conf |grep -v '#' |grep -e 'filter' -e 'types'
filter = [ "a|/dev/mpath/.*/|","a|/dev/mapper/.*|", "a|/dev/sda|","r|/dev/sd[b-z]|", "r/.*/" ]
types = [ "device-mapper", 1]
#cat /etc/multipath.conf |grep -v '#'
devnode_blacklist {
devnode "^sda"
}
defaults {
user_friendly_names yes
}
multipaths {
multipath {
wwid 360060160f1731100c642e85121b2dd11
alias mpath0
}
multipath {
wwid 360060160f173110012f68b1e56b3dd11
alias mpath1
}
multipath {
wwid 360060160f17311000c55033921b2dd11
alias mpath2
}
multipath {
wwid 360060160f1731100b254eb42b9b4dd11
alias mpath3
}
}