Your message dated Mon, 19 May 2014 11:19:17 -0400 with message-id <[email protected]> and subject line Re: Bug#714570: Make mke2fs warn before destroying an existing fs/LVM container has caused the Debian Bug report #714570, regarding Make mke2fs warn before destroying an existing fs/LVM container to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 714570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714570 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: e2fsprogs Version: 1.42.8-1 I accidentally ran e2fsck on a partition which actually held a volume group without running vgchange on it first. The result seemed to be that e2fsck thought there was a problem (I don't now recall exactly what it was, unfortunately), I asked it to fix it, then realised my mistake, but it was too late - vgchange no longer recognised the partition as containing a volume group. Recovering the situation was too much effort - I just reformatted the disk instead (having already made a backup of the data). If it is at all feasible, it would be great if e2fsck could check for the presence of a volume group and warn before making any "fixes" which might destroy the volume group. I hope this makes sense. Julian
--- End Message ---
--- Begin Message ---Package: e2fsprogs Version: 1.42.10-1 This wishlist bug has been fixed in 1.42.10. - Ted
--- End Message ---
