Now that 'relatime' is pushed to all major distribuitons, should we just document and discourage 'noatime' ? (At least for SAN Boot) Apart from Backup softwares and tmpclean, I can't recollect any other user of it. OTOH LUNs would be easily backed by users on the target. Ritesh ________________________________ From: George, Martin Sent: Tuesday, January 22, 2008 9:00 PM To: k-ueda@xxxxxxxxxxxxx Cc: Sarraf, Ritesh Subject: Root device multipathed host freeze with the latest upstream multipath-tools package Hi Kiyoshi, I took the latest upstream multipath-tools package (Jan 15, 2008) and installed it on my RHEL 5.1 host to verify the libprio fix. To simulate the FCP path faults, I ran your script (as attached in the mail) which alternately offlined/onlined the corresponding SCSI paths of the root dm device in the syfs. Listing my observations below: 1) The freeze was still reproducible. On checking the sysrq dumps (as attached), I could see it was the script itself i.e. test.sh which seems to have stalled on the exec () system call perhaps waiting for inode write out for updated access time (the script resides on my root dm device itself). As suggested by you in the bugzilla, I remounted the root device using the noatime option and then reran the script - I have not hit the freeze yet. Is this the expected behavior? 2) With the latest upstream multipath-tools package, "multipath -ll" displays all paths with the same priority - I am not able to prioritize paths into primary/secondary despite the normal group_by_prio setting. Does the libprio fix alter the behavior here? Wanted to know your comments on the same. Thanks a lot, -Martin -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
