similar to: ext3 file system becoming read only

I''ve compiled the 3.0-devel version on SUSE Linux 9.3. The ony problem is the qla2300 driver, which will not start all correctly on boot. So i cannot see other partitions than sda. --------------------------------------------------------------------------------- QLogic Fibre Channel HBA Driver ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 24 (level, low) -> IRQ 185 qla2300

Hi, We are running a server as an nfs head connect to a clariion, every couple of days we have our box fall over with the following msg in syslog. Has anyone had this happen to there boxen? rhel4 u4 May 8 12:23:52 ruchba kernel: Assertion failure in log_do_checkpoint() at fs/jbd/checkpoint.c:363: "drop_count != 0 || cleanup_ret != 0" May 8 12:23:52 ruchba kernel: ------------[ cut

Here''s the latest USB code against the xen 3.0.0 release. Since the last posting this version updates the code to use the new 32 bit grant references and the latest GNTTABOP_map_grant_ref definition. I''ve also changed the definition of the virtual USB HCD to have a single port rather than seven ports with six unused. Domains importing multiple USB devices will get a HCD for

Hi All, we are using Red Hat 2.1 Kernel e38 along with MSA 1000. ocfs version being used is $ rpm -qa | grep ocfs ocfs-tools-1.0.10-1 ocfs-2.4.9-e-enterprise-1.0.12-1 ocfs-support-1.0.10-1 Database Version is 9.2.0.5 However we find that the performance of the database on OCFS is too slow. even a select count(1) from all_tables takes like a while to complete. We initially assumed RAC is

Red Hat is pleased to announce the availability of Update 2 for the Red Hat Enterprise Linux 4 family of products, including: - Red Hat Enterprise Linux AS 4 for x86, AMD64/EM64T, Itanium, POWER, S/390 and zSeries - Red Hat Enterprise Linux ES 4 for x86, AMD64/EM64T, Itanium - Red Hat Enterprise Linux WS 4 for x86, AMD64/EM64T, Itanium - Red Hat Desktop 4 for x86 and AMD64/EM64T Craig

Hi, Im trying to set create a RHAS4 DomU on a HP proliant 360DL 4 processor SMP. Since the xenified kernel that came with FC4 didnt work, I compiled a xen-unstable enabled kernel for FC4. all was fine untill it gave me a ''unable to open an initial console'' I tried to make an initrd for my xen0 kern but it didnt work. So I tried using the old initrd image that I had and Dom0

Can anyone point me to a "Writing Puppet recipes for Dummies" doc? I''m trying to do a basic probe using lspci to see if I have a Qlogic HBA installed on the machine, and if so, install the Qlogic scli package. Here''s a shell script of what I''m trying to do: #!/bin/bash vendor=1077 # QLogic model=2422 # 24xx hba /sbin/lspci -n -d $vendor:$model | grep

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

Hello, I''m doing one emergencial migrate for one very old machine, because we will have one IMPLOSION (!!!) very close from here, and I''m thinking that this old IDE disk will not survive... :-/ [root@registro-2 /root]# df -h Filesystem Size Used Avail Use% Mounted on /dev/ida/c0d0p2 3.8G 2.3G 1.4G 62% / /dev/ida/c0d0p8 26G 20G 4.4G 82% /data

> > Well, i''m using here the qla2340 on several boxes. It works > > with Xen 2.0 but noch with Xen 3.0. as part of SUSE Linux 10.0: > > Interesting. If the driver really doews work flawlessly in > Xen 2, then I think the culprit has to be interrupt routeing. > > Under Xen 3, does /proc/interrupts show you''re receiving interrupts? I cannot boot with

> > Well, i''m using here the qla2340 on several boxes. It works > > with Xen 2.0 but noch with Xen 3.0. as part of SUSE Linux 10.0: > > Interesting. If the driver really doews work flawlessly in > Xen 2, then I think the culprit has to be interrupt routeing. > > Under Xen 3, does /proc/interrupts show you''re receiving interrupts? I cannot boot with

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

I''ve compiled xen without any problems. but now i have to create an initrd file. When i use the command mkinitrd (without any options) the i''ve got some errors: # mkinitrd Root device: /dev/sda3 (mounted on / as reiserfs) Module list: ata_piix mptbase mptscsih qla2300 reiserfs Kernel image: /boot/vmlinuz-2.6.11.12-xen0 Initrd image: /boot/initrd-2.6.11.12-xen0 Shared

Hi, I''m on a HP DL365, amd64, running SLES10sp1, but with kernel and xen of SLES10sp2, therefore using Xen 3.2. The domU shall be a Windows HVM guest. I want use the Qlogic SAN card in a domU. I''m following these instructions: http://www.novell.com/communities/node/2880/assign-dedicated-network-card-or-pci-device-xen-virtual-machine well, there is written that this only

All, We are encountering spurious errors with ext3. After some period of heavy IO we may see messages similiar to: EXT3-fs error (device cciss/c0d0p5) in start_transaction: Journal has aborted When this happens the filesystem is remounted read-only. If it's the root filesystem the system becomes unresponsive and must be rebooted. An fsck on the affected filesystem shows lots of corruption.

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; > } >

hi, anyone to know a tool that will display more friendly output ... probably a tree like structure (if no cross sections occur)... OR a top like output... thanx raptor _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

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