[DRBD-user] /dev/drbd0: Failure: (132) The sync-after minor number is invalid

Lars Ellenberg lars.ellenberg at linbit.com
Thu Feb 5 12:06:00 CET 2009

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


On Thu, Feb 05, 2009 at 11:29:49AM +0100, Raoul Bhatia [IPAX] wrote:
> hello lars,
> 
> Lars Ellenberg wrote:
> >> if i only do a "drbd up www" after reboot, i get:
> >>> # drbdadm up www
> >>> /dev/drbd0: Failure: (132) The sync-after minor number is invalid
> >>> Command 'drbdsetup /dev/drbd0 syncer --set-defaults --create-device
> --rate=50M --after=1 --al-extents=257' terminated with exit code 10
> >
> > you tell it to sync after drbd1 (--after=1,
> > syncer { after "mysql" } in your drbd.conf file).
> > only that does not (yet) exist.
> > so, it is "invalid" - at that point in time.
> 
> ok, this "makes sense". so i guess that this is a non fatal error,
> right? what i wanted to achieve is: "in case of resync, resync the
> smallest device first. then proceed with the next biggest one".
> 
> is this possible?
> 
> besides that (if this is a non-fatal error), as far as i understand the
> source, print_config_error() will return rc 10 for any valid error
> (means: "err_no > RetCodeBase").
> 
> should we not distinguish fatal and non-fatal errors here?
> 
> and last but not least, what about using defines for the error codes and
> describing them in the user-guide. it makes searching and understanding
> so much easier :)

patches accepted.
http://git.drbd.org/drbd-8.3.git
http://git.drbd.org/drbd-documentation.git

 ;)

-- 
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
__
please don't Cc me, but send to list   --   I'm subscribed



More information about the drbd-user mailing list