On Thu, Apr 23, 2009 at 07:08:57PM +0200, Guido Trotter wrote: > On Thu, Apr 23, 2009 at 6:55 PM, Iustin Pop <[email protected]> wrote: > > > > When a remote node returns invalid LVM data, we check it, but we don't > > stop and continue with the rest of the checks (which require a valid > > volume group). This raises an internal error and breaks verify disks. > > > > This seems unchanged for a long while, I don't know why it surfaced just > > recently. > > Perhaps we didn't try it with invalid LVM data?
I don't believe that 1.2 didn't happen upon this case; rather that, since we didn't have jobs, and disks-verify is run in the background by the watcher, its errors were simply ignored. > LGTM thanks! iustin
