From owner-freebsd-current@FreeBSD.ORG Fri Jan 18 11:39:36 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7BA6F806; Fri, 18 Jan 2013 11:39:36 +0000 (UTC) (envelope-from satan@ukr.net) Received: from hell.ukr.net (hell.ukr.net [212.42.67.68]) by mx1.freebsd.org (Postfix) with ESMTP id D9133C; Fri, 18 Jan 2013 11:39:35 +0000 (UTC) Received: from satan by hell.ukr.net with local ID 1TwAII-000FmS-7w ; Fri, 18 Jan 2013 13:39:34 +0200 Date: Fri, 18 Jan 2013 13:39:34 +0200 From: Vitalij Satanivskij To: Alexander Motin Subject: Re: panic after r244584 Message-ID: <20130118113934.GA60441@hell.ukr.net> References: <20130118073600.GA70874@hell.ukr.net> <20130118094424.GD2331@FreeBSD.org> <50F93165.60809@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50F93165.60809@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: jh@freebsd.org, Vitalij Satanivskij , Gleb Smirnoff , freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: satan@ukr.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jan 2013 11:39:36 -0000 Alexander Motin wrote: AM> On 18.01.2013 11:44, Gleb Smirnoff wrote: AM> > On Fri, Jan 18, 2013 at 09:36:00AM +0200, Vitalij Satanivskij wrote: AM> > V> After upgrading server from old hardware/software to freebsd current (## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/245479), AM> > V> system hung's with message - AM> > V> panic: make_dev_alias_v: bad si_name (error=22 si_name=enc@n5003048000bab37d/tpe0/slot@1/elmdesc@Slot 01/pass7) AM> > AM> > EINVAL (22) is caused by space character in the si_name: AM> > AM> > si_name=enc@n5003048000bab37d/tpe0/slot@1/elmdesc@Slot 01/pass7 AM> > AM> > I think Alexander (in Cc) has idea on why did that happen and how AM> > should that be fixed. AM> AM> The panic is triggered by the check added by the recent r244584 change. AM> The space in device name came from the enclosure device, and I guess it AM> may be quite often situation. Using human readable name supposed to help AM> system administrators, but with spaces banned that may be a problem. AM> That's was not created by human, it was generated (I think so) by system. May be problem not in r244584 at all but in incorect generation of the si_name ? More info drive (actualy drives, all 36 have same problem) inserted in backplane on supermicro chasis with "LSI CORP SAS2X36 0417" on board. All of them attached to lsi sas 9211-4i controler in HBA mode.