Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Linux\s+\&\s+SAN\s+Device\s+Interruptions\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Linux\s+\&\s+SAN\s+Device\s+Interruptions\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: [ADSM-L] Linux & SAN Device Interruptions (score: 1): Author: Remco Post <r.post AT PLCS DOT NL>; Date: Tue, 19 Apr 2011 14:09:59 +0200; Hi Nick, linux has to possibility of hot-adding scsi (fc, sas) devices by talking to /proc/scsi/scsi, modern kernels do that better than older ones, where you have to add each individual device manua; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2011-04/msg00114.html (12,913 bytes)
2. [ADSM-L] Linux & SAN Device Interruptions (score: 1): Author: Nick Laflamme <dplaflamme AT GMAIL DOT COM>; Date: Tue, 29 Mar 2011 18:23:34 -0500; How are those of you who run TSM servers or storage agents on Linux on Intel doing with disruptions with SAN-attached tape devices or the SAN fabric itself? In my current shop, we run TSM servers on; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2011-03/msg00276.html (12,060 bytes)
3. Re: [ADSM-L] Linux & SAN Device Interruptions (score: 1): Author: Robert Clark <robert.clark7 AT USBANK DOT COM>; Date: Wed, 30 Mar 2011 08:41:02 -0700; Hi Nick, I don't claim to have slayed that particular dragon yet, but I have uncovered some background info on the subject: In our case we're running a mix of RHEL (RHES?) 4 & 5 (on Intel x86_64) on; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2011-03/msg00286.html (15,049 bytes)

Current List: 1 - 3
Page: [1]