similar to: SUMMARY : Repair Filesystem prompt , after inode has illegal blocks ; qla2xxx message on reboot

hi All, Re below - thanks for the replies to the fsck question. I have run fsck -r /data and this eventually completed with several changes made. Now I am getting the following error from the qla2xxx driver on boot . . . qla2xxx 0000:05:0d.0: Mailbox command timeout occured. Scheduling ISP abort. qla2xxx 0000:05:0d.0: Mailbox command timeout occured. Scheduling ISP abort. . etc . It looks

hi All, A fault on our SAN dropped us down to a read-only filesystem and after reboot, we have an "Unexpected Inconsistency" and I am being instructed by the boot to run fsck manually without -a or -p (this was after I think processing around 15% of the filesystem) The specific message is "inode 27344909 has illegal blocks" I recall running fsck some years ago on smaller

I wanted to post this in case there is a real bug here. The system this is on is running Debian Etch with the Xen packages from Debian Unstable (currently 3.0.2+hg9697-1). I am running all packaged software so this is probably slightly out of date. This is on an HP DL320 G4 with a Pentium D 930 processor. I tried unloading and reloading the qla2xxx module, but rmmod reported it in use, however

> I wanted to post this in case there is a real bug here. > > The system this is on is running Debian Etch with the Xen packages from > Debian Unstable (currently 3.0.2+hg9697-1). I am running all packaged > software so this is probably slightly out of date. It would be interesting to see if this can be repro''ed on a tree built from a recent xen-unstable.hg.

I am trying to dedicate a number of PCI ports to DomU and no success! The PCI devices I am trying to dedicate are QLogic 23xx cards! I am using SUSE 10.1 with latest xen-unstable! I have followed all the instructions given in latest xen 3.0 manual. Like building the backend support in Dom0 Building the frontend support in DomU Using the pciback.hide=(xx:xx.x) in Dom0 command

Maybe one of you has experienced something like this before. I have a host running CentOS5.3, x86_64 version with the standard qla2xxx driver. Both ports are recognized and show output in dmesg but they never find my storage device: qla2xxx 0000:07:00.1: LIP reset occured (f700). qla2xxx 0000:07:00.1: LIP occured (f700). qla2xxx 0000:07:00.1: LIP reset occured (f7f7). qla2xxx 0000:07:00.0: LOOP

CentOS Errata and Enhancement Advisory 2016:0682 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-0682.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: beb8bae27284f3d614fc06a783956a67bdf4954962014a9e79e6dca337a4d65f kmod-qla2xxx-8.07.00.26.06.8_k-1.el6_7.i686.rpm x86_64:

CentOS Errata and Enhancement Advisory 2016:1375 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-1375.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 08a6bc752e27c15e9416e7e517f3d8196230222a0b48500feabb503a51526233 kmod-qla2xxx-8.07.00.33.07.3_k-1.el7_2.x86_64.rpm Source:

On Tue, 2018-05-15 at 09:00 -0700, Matthew Wilcox wrote: > diff --git a/drivers/scsi/qla2xxx/qla_target.c b/drivers/scsi/qla2xxx/qla_target.c > index 025dc2d3f3de..cdf671c2af61 100644 > --- a/drivers/scsi/qla2xxx/qla_target.c > +++ b/drivers/scsi/qla2xxx/qla_target.c > @@ -3719,7 +3719,8 @@ void qlt_free_cmd(struct qla_tgt_cmd *cmd) > return; > } >

On Tue, 2018-05-15 at 09:00 -0700, Matthew Wilcox wrote: > diff --git a/drivers/scsi/qla2xxx/qla_target.c b/drivers/scsi/qla2xxx/qla_target.c > index 025dc2d3f3de..cdf671c2af61 100644 > --- a/drivers/scsi/qla2xxx/qla_target.c > +++ b/drivers/scsi/qla2xxx/qla_target.c > @@ -3719,7 +3719,8 @@ void qlt_free_cmd(struct qla_tgt_cmd *cmd) > return; > } >

On 12/07/16 21:54, Michael S. Tsirkin wrote: > On Thu, Dec 08, 2016 at 05:21:47AM +0000, Bart Van Assche wrote: >> Additionally, there are notable exceptions to the rule that most drivers >> are endian-clean, e.g. drivers/scsi/qla2xxx. I would appreciate it if it >> would remain possible to check such drivers with sparse without enabling >> endianness checks. Have you

On 12/07/16 21:54, Michael S. Tsirkin wrote: > On Thu, Dec 08, 2016 at 05:21:47AM +0000, Bart Van Assche wrote: >> Additionally, there are notable exceptions to the rule that most drivers >> are endian-clean, e.g. drivers/scsi/qla2xxx. I would appreciate it if it >> would remain possible to check such drivers with sparse without enabling >> endianness checks. Have you

Hi In our office environment few servers mostly database servers and yesterday it happened for one application server(first time) the partion is getting "read only". I was checking the archives, found may be similar kind of issues in the 2007-July archives. But how it has been solved if someone describes me that will be really helpful. In our case, just at the problem started found

hi all We have a rh linux server connected to two HP SAN controllers, one an HSV200 (on the way out), the other an HSV400 (on the way in). (Via a Qlogic HBA). /etc/multipath.conf contains this : device { vendor "(COMPAQ|HP)" product "HSV1[01]1|HSV2[01]0|HSV300|HSV4[05]0" getuid_callout "/sbin/scsi_id -g -u -s /block/%n"

I''m wondering if anyone might have any suggestions... We''ve installed CentOS5.2 on 3 servers and have an FC switch, dual-port cards, and FC RAID device. We configured the RAID as two separate logical RAIDs. One is RAID-10 for speed and it hosts Xen VM images as LVs. The rest of the drive is RAID-5 to maximize space and houses a lot of lighter access data on a GFS2 filesystem.

On 12/07/16 18:29, Michael S. Tsirkin wrote: > By now, linux is mostly endian-clean. Enabling endian-ness > checks for everyone produces about 200 new sparse warnings for me - > less than 10% over the 2000 sparse warnings already there. > > Not a big deal, OTOH enabling this helps people notice > they are introducing new bugs. > > So let's just drop __CHECK_ENDIAN__.

On Tue, 2018-06-12 at 09:15 -0700, Matthew Wilcox wrote: > On Tue, Jun 12, 2018 at 03:22:42PM +0000, Bart Van Assche wrote: > > On Tue, 2018-05-15 at 09:00 -0700, Matthew Wilcox wrote: > > > diff --git a/drivers/scsi/qla2xxx/qla_target.c b/drivers/scsi/qla2xxx/qla_target.c > > > index 025dc2d3f3de..cdf671c2af61 100644 > > > ---

Hello, I'm just beginning to learn R. What books/online learning modules with datasets would you suggest? Thank you! Best wishes, Michael ____________________________________ Michael McCulloch Pine Street Clinic Pine Street Foundation 124 Pine Street, San Anselmo, CA 94960-2674 tel 415.407.1357 fax 415.485.1065 email: mm at pinest.org web: www.pinest.org

Hi, I use?R to draw my graphs. I have 100 points on a simple xy-plot. The points are distinguished by a third variable which is categorical with 10 levels. I have been plotting x against y and using gray scales to distinguish the level of the categorical variable for each point. It looks ok to me but?a journal reviewer says this is not any use. I cannot afford to pay for colour prints. Any