RE: generating a Linux WWN?
Unfortunately, it looks like IEEE doesn't have any OID's registered for Linux or other reserved areas (http://standards.ieee.org/regauth/oui/oui.txt). However, it does look like they go in order... so maybe if you used an OID of 0xFF you could at least guarantee that you didn't conflict with any company's SAS WWNs. Patrick Boyd James Smart wrote: Uh, although this may work very well for small constrained configs, as one who debugs larger environments (and things always grow or get connected in ways you don't expect), depending on a random number for uniqueness makes me very unsettled. Debugging that small-percentage potential, when/if it does occur can be an absolute nightmare with all kinds of weird behavior. Rarely will you solve it from the context of a single server. There are lots of ways to cheat, but I believe they all have to be based on some small part that is guaranteed to be unique (like the IEEE id's). -- james s Jeff Garzik wrote: Is there an accepted way to generate a SAS address, when the adapter does not supply one (NVRAM invalid or missing, etc.)? Unless somebody complains, I was just planning to use get_random_bytes(). But maybe Linux has an IEEE id we can use, to make the practice a bit more legitimate and avoid stomping on others? Or an IEEE id specifically designed for generated-address purposes? Jeff - To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html - To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html - To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH]mpt fusion: add sysfs attributes to display IOC parameters
diff -Naurp b/drivers/message/fusion/mptbase.h a/drivers/message/fusion/mptbase.h --- b/drivers/message/fusion/mptbase.h 2007-07-02 16:20:46.0 +0530 +++ a/drivers/message/fusion/mptbase.h 2007-07-03 18:13:28.0 +0530 @@ -78,6 +78,10 @@ #define MPT_LINUX_VERSION_COMMON 3.04.05 #define MPT_LINUX_PACKAGE_NAME@(#)mptlinux-3.04.05 #define WHAT_MAGIC_STRING @ ( # ) +#define MPT_LINUX_MAJOR_VERSION 3 +#define MPT_LINUX_MINOR_VERSION 04 +#define MPT_LINUX_BUILD_VERSION 05 +#define MPT_LINUX_RELEASE_VERSION 00 You have the version information listed 3 times. Can't you just build MPT_LINUX_VERSION_COMMON and MPT_LINUX_PACKAGE_NAME? - To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: no disk drive detected at boot time
You might want to take a look at this. http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/54a1ca21b839ebf1/4a0cd669217f3c7d?lnk=strnum=1#4a0cd669217f3c7d According to that email you need firmware 6.61 or lower to use the current megaraid-mm and mbox drivers, however apparently this firmware doesn't support disks greater than 128GB in size. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jean-Max Reymond Sent: Monday, January 15, 2007 4:45 AM To: linux-scsi@vger.kernel.org Subject: Re: no disk drive detected at boot time Jean-Max Reymond a écrit : hi, The computer is an DELL 1600SC with SATA RAID. At boot time, no disk are detected. I have tried with Ubuntu Edgy and Fedora Core 6 and I have the same troubles. Fedora Core 2 is running on the computer. it seems that Dell CERC ATA100/4ch is not supported by any driver. see http://www.mail-archive.com/debian-kernel@lists.debian.org/msg20989.ht ml no answers ? here is the report of cat /proc/scsi/scsi : Host: scsi3 Channel: 00 Id: 00 Lun: 00 Vendor: MegaRAID Model: LD 0 RAID5 714G Rev: 6.62 Type: Direct-AccessANSI SCSI revision: 02 does it exist a recent patch ? thanks for your tips - To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH 5/6] fusion: bump version
Is there a reason that you have the version information in two different places instead of just concatinating the strings together? Patrick Boyd Dell Storage Software Engineer (512)728-3182 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Moore Sent: Thursday, January 04, 2007 9:49 PM To: linux-scsi@vger.kernel.org; [EMAIL PROTECTED] Subject: [PATCH 5/6] fusion: bump version bump version Signed-off-by: Eric Moore [EMAIL PROTECTED] diff -uarpN b/drivers/message/fusion/mptbase.h a/drivers/message/fusion/mptbase.h --- b/drivers/message/fusion/mptbase.h 2006-12-25 01:41:05.0 -0700 +++ a/drivers/message/fusion/mptbase.h 2006-12-25 01:45:41.0 -0700 @@ -75,8 +75,8 @@ #define COPYRIGHT Copyright (c) 1999-2007 MODULEAUTHOR #endif -#define MPT_LINUX_VERSION_COMMON 3.04.02 -#define MPT_LINUX_PACKAGE_NAME @(#)mptlinux-3.04.02 +#define MPT_LINUX_VERSION_COMMON 3.04.03 +#define MPT_LINUX_PACKAGE_NAME @(#)mptlinux-3.04.03 #define WHAT_MAGIC_STRING @ ( # ) #define show_mptmod_ver(s,ver) \ - To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html - To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
