xfs
[Top] [All Lists]

Re: [BUG]XFS at CONFIG_SCSI_MULTI_LUN

To: linux-xfs@xxxxxxxxxxx
Subject: Re: [BUG]XFS at CONFIG_SCSI_MULTI_LUN
From: Fang Han <dfbb@xxxxxxxxxxxx>
Date: Fri, 19 Oct 2001 10:24:49 +0800
In-reply-to: <200110182105.f9IL5Pn01679@xxxxxxxxxxxxxxxxxxxx>; from lord@xxxxxxx on Thu, Oct 18, 2001 at 04:05:25PM -0500
Mail-followup-to: linux-xfs@xxxxxxxxxxx
References: <dfbb@xxxxxxxxxxxx> <200110182105.f9IL5Pn01679@xxxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
> 
> Well, first you have to explain what the MULTI_LUN thing does, because I
> have no idea. However, from XFS's point of view, a device is a device
> is a device - unless it is LVM. There are some differences there in
> terms of how we do disk I/O to the log.


>From kernel help 
"If you have a SCSI device that supports more than one LUN (Logical      
Unit Number), e.g. a CD jukebox, and only one LUN is detected, you      
can say Y here to force the SCSI driver to probe for multiple LUNs.     
A SCSI device with multiple LUNs acts logically like multiple SCSI      
devices. The vast majority of SCSI devices have only one LUN, and       
so most people can say N here and should in fact do so, because it      
is safer. "

MULTI_LUN is using to probe multi device on one scsi channel.
        

> 
> I would ask that you try a later kernel, there have been changes in
> all sorts of things since the 1.0.1 release, there is every chance it
> is fixed by some other kernel change. If not, there is probably not a
> lot we can do about it, the disk I/O involved in mount is pretty
> fixed (a binary chop scan of the log blocks looking for the head and
> tail of the log).

I will test it an report it later.

> 
> Steve
> 
> 
> 
> 


<Prev in Thread] Current Thread [Next in Thread>