Luca Berra wrote: > i meant that LVM (actually device-mapper) does not do anything special. > it just passes the IO requests from the fs layer to the > underlying block device and if the underlyng block device returns an IO > error then it is passed back to the fs. which will cause ext2 to remount > the filesystem readonly. Hi, Thanks for clarifying. In my case, the block device is hidden by the multipathing layer. It is something like: (Block Device(Multipathing(LVM(Filesystem) ) ) ) Now during takeover/giveback, the multipathing layer is intelligent enough to wait till <120 seconds before declaring that the path has really gone offline and no more paths are available. If within the 120 seconds time span, the takeover succeeds, the path is back online and everything works fine in a non-LVM setup. It is only in an LVM setup that a takeover/giveback ends up with the host OS having a filesystem read-only problem. Now if I go with your explanation, I shouldn't have had the filesystem read-only problem since the I/O is being passed on to the multipathing layer which is intelligent enough to wait for N seconds before really sending an I/O Error. Are there any timeout options in LVM to allow it to wait for N seconds before sending out an error ? (I understand that LVM might not be involved, but just wondering). Thanks, Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention." "Stealing logic from one person is plagiarism, stealing from many is research." "The great are those who achieve the impossible, the petty are those who cannot - rrs" _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
