-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pvmove wrong logic on corner case #119
Comments
So the returned status value cannot be qualified as bug and this is more a philosophical question and there is no clear definition in logic - i.e. many 'lvchange' command will give you an error if you try to change something into the state in which the LV already is. Note - in the case it would first check 'extents' for moving - it gives this error message: So in most cases 'lvm2' does report an error if the command could not be doing what it was asking to be doing - it does NOT usually try to 'sanitize' commands working with metadata and report 'success' if there is nothing to do. We would likely need to introduce some new set of options, but it's usually not worth.... |
I have two PVs and one VG over them. First PV is empty (no allocated PE). The second is full (all PEs allocated, no free PEs).
pvmove /dev/first_pv
exits with non-zero code sayingNo extents available for allocation.
It should check first if there is nothing to do. And only THEN check for extents available for allocation.
The text was updated successfully, but these errors were encountered: