Date: Fri, 18 Jan 2013 13:26:29 +0200 From: Alexander Motin <mav@FreeBSD.org> To: Gleb Smirnoff <glebius@FreeBSD.org> Cc: Vitalij Satanivskij <satan@ukr.net>, freebsd-current@FreeBSD.org, jh@freebsd.org Subject: Re: panic after r244584 Message-ID: <50F93165.60809@FreeBSD.org> In-Reply-To: <20130118094424.GD2331@FreeBSD.org> References: <20130118073600.GA70874@hell.ukr.net> <20130118094424.GD2331@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18.01.2013 11:44, Gleb Smirnoff wrote: > On Fri, Jan 18, 2013 at 09:36:00AM +0200, Vitalij Satanivskij wrote: > V> After upgrading server from old hardware/software to freebsd current (## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/245479), > V> system hung's with message - > V> panic: make_dev_alias_v: bad si_name (error=22 si_name=enc@n5003048000bab37d/tpe0/slot@1/elmdesc@Slot 01/pass7) > > EINVAL (22) is caused by space character in the si_name: > > si_name=enc@n5003048000bab37d/tpe0/slot@1/elmdesc@Slot 01/pass7 > > I think Alexander (in Cc) has idea on why did that happen and how > should that be fixed. The panic is triggered by the check added by the recent r244584 change. The space in device name came from the enclosure device, and I guess it may be quite often situation. Using human readable name supposed to help system administrators, but with spaces banned that may be a problem. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50F93165.60809>