<p>Sadly it's bullet biting time. <br>
</p>
<div class="gmail_quote">On Jan 11, 2011 12:16 PM, "Brian Pitts" <<a href="mailto:brian@polibyte.com">brian@polibyte.com</a>> wrote:<br type="attribution">> Hi,<br>> <br>> I have a server whose link to an iSCSI volume was interrupted for so<br>
> long that writes were lost and the volume was remounted read-only.<br>> <br>> kernel: Buffer I/O error on device sdf1, logical block 1<br>> 0174<br>> kernel: lost page write due to I/O error on sdf1<br>> kernel: Aborting journal on device sdf1.<br>
> <br>> A long-running series of processes are currently using the volume<br>> without problems, but of course they will blow up if they try to write<br>> anything to it. I thought I might be able to remount it read-write<br>
> without unmounting it first, but this isn't the case.<br>> <br>> If I try "mount -o remount,rw /mnt/foo", I'm told<br>> "mount: block device /dev/disk/by-label/foo is write-protected, mounting<br>
> read-only" and "EXT3-fs error (device sdf1): ext3_remount: Abort forced<br>> by user" is logged.<br>> <br>> Does anyone have any other ideas, or do I need to bite the bullet and<br>> interrupt the running job to unmount and remount the volume?<br>
> <br>> -- <br>> All the best,<br>> Brian Pitts<br>> _______________________________________________<br>> Ale mailing list<br>> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>> <a href="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</a><br>
> See JOBS, ANNOUNCE and SCHOOLS lists at<br>> <a href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a><br></div>