Ext3 filesystems on san become read only

08-16-2014

Registered User

50, 5

Join Date: Nov 2008

Last Activity: 2 March 2020, 5:57 AM EST

Location: Mexico CDMX

Posts: 50

Thanks Given: 0

Thanked 5 Times in 5 Posts

Hi Mig28mx,

if you can confirm that the issue is present when the second PATH is active, probably your problem is the compatibility of linux native multipath with the storage system.

For example, if your Storage Array is a HighEnd ( EMC VMAX, HDS VSP, DS8000), normally, the multipath daemon is fully compatible with default settings.

However if you Storage is a midrage (EMC VNX, HDS HUS or AMS), you need write special settings inf the multipath.conf. You need review the notes about of this setting in the User Guide of the Storage Array.

If the issue continue, I think that you need review the SAN Switches in order to see if the error counters in the fibre ports are growing.

If you can share with me the model of switches and storage I can be more precise.

cerber0

View Public Profile for cerber0

Find all posts by cerber0

FSCK(8) BSD System Manager's Manual FSCK(8) NAME
fsck -- filesystem consistency check and interactive repair SYNOPSIS
fsck -p [-f] fsck [-l maxparallel] [-q] [-y] [-n] [-d] DESCRIPTION
The first form of fsck preens a standard set of filesystems or the specified filesystems. It is normally used in the script /etc/rc during automatic reboot. Here fsck reads the filesystem descriptor table (using getfsent(3)) to determine which filesystems to check. Only parti- tions that have ``rw,'' ``rq'' or ``ro'' as options, and that have non-zero pass number are checked. Filesystems with pass number 1 (nor- mally just the root filesystem) are checked one at a time. When pass 1 completes, all remaining filesystems are checked, running one process per disk drive. The disk drive containing each filesystem is inferred from the shortest prefix of the device name that ends in one or more digits; the remaining characters are assumed to be the partition designator. In preening mode, filesystems that are marked clean are skipped. Filesystems are marked clean when they are unmounted, when they have been mounted read-only, or when fsck runs on them success- fully. It should be noted that fsck is now essentially a wrapper that invokes other fsck_XXX utilities as needed. Currently, fsck can invoke fsck_hfs, fsck_apfs, fsck_msdos, fsck_exfat, and fsck_udf. If this underlying process that fsck invokes encounters serious inconsistencies or the filesystem type is not one of the above, it exits with an abnormal return status and an automatic reboot will then fail. For each corrected inconsistency one or more lines will be printed identifying the filesystem on which the correction will take place, and the nature of the correction. If sent a QUIT signal, fsck will finish the filesystem checks, then exit with an abnormal return status that causes an automatic reboot to fail. This is useful when you want to finish the filesystem checks during an automatic reboot, but do not want the machine to come up multi- user after the checks complete. Without the -p option, fsck audits and interactively repairs inconsistent conditions for filesystems. It should be noted that some of the corrective actions which are not correctable under the -p option will result in some loss of data. The amount and severity of data lost may be determined from the diagnostic output. If the operator does not have write permission on the filesystem fsck will default to a -n action. The following flags are interpreted by fsck and passed along to the underlying tool that it spawns. -f Force fsck to check `clean' filesystems when preening. -l Limit the number of parallel checks to the number specified in the following argument. By default, the limit is the number of disks, running one process per disk. If a smaller limit is given, the disks are checked round-robin, one filesystem at a time. -R Specify a particular passno number for which fsck is to check. You may only specify 1 or 2. Only those filesystems matching that particular passno entry (if using fstab) will be checked. For more information on the passno field, see fstab(5). -p "Preen" mode, described above. -q Do a quick check to determine if the filesystem was unmounted cleanly. -y Assume a yes response to all questions asked by fsck; this should be used with great caution as this is a free license to con- tinue after essentially unlimited trouble has been encountered. -n Assume a no response to all questions asked by fsck except for 'CONTINUE?', which is assumed to be affirmative; do not open the filesystem for writing. If no filesystems are given to fsck then a default list of filesystems is read using getfsent(3). Because of inconsistencies between the block device and the buffer cache, the raw device should always be used. SEE ALSO
fs(5), fsck_hfs(8), fsck_apfs(8), fsck_msdos(8), getfsent(3), fstab(5,) reboot(8) 4th Berkeley Distribution May 18, 2010 4th Berkeley Distribution

Red Hat

Ext3 filesystems on san become read only

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Faster way: SAN hd to SAN hd copying

Discussion started by: rino19ny

2. Solaris

Warnings about read-only filesystems while installing a Solaris package

Discussion started by: snreddy_gopu

3. AIX

IBM SAN TO SAN Mirroring

Discussion started by: filosophizer

4. Solaris

Empty ZFS SAN file system with high read I/O using MPXIO

Discussion started by: christr

5. UNIX for Dummies Questions & Answers

Read only filesystems

Discussion started by: karlochacon

6. UNIX for Dummies Questions & Answers

Mounting fs ext3

Discussion started by: CasperQuiet

7. Solaris

Thoughts/experiences of SAN attaching V880 to EMC SAN

Discussion started by: si_linux

8. UNIX for Dummies Questions & Answers

/ext2 and /ext3

Discussion started by: vasikaran

9. Filesystems, Disks and Memory

ReiserFS vs ext3 vs anything else?

Discussion started by: fishsponge

10. Filesystems, Disks and Memory

ext3 filesystem

Discussion started by: comadreja

LEARN ABOUT MOJAVE

fsck