Thank you for your post. I assume it won't change your opinion on this problem. But just to correct my post. I made an incorrect statement. When the problem occured the application was copying from the snapshot to the vmbackup volume. Therefore the 1GB was read from the snapshot, and not writen to the snapshot as I said previously.
To my knowledge it seem impossible that the snapshot was full. Plus, I always thought that a full snapshot was automatically disabled, but the file system would remain usable. In this case, no report in the log, and the complete lvm2 group volume became NOT usable (read/write hang). Including the second volume not involved in the snapshot. I can't believe that a full snapshot would affect other lvm2 volumes, but I guess it maybe possible ???? Thanks anyway. Phil Ten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org