Re: [gentoo-user] Weird Buffer I/O error in dev ndb0
Phill MV wrote: Well, *something* is trying to access a function that doesnt exist in NDB; whether we know what it does or why, I'm guessing it's a behaviour that shouldn't happen :P. I suppose whatever tries to access NDB has a bug in it... but what would that be? Do you have lvm installed (/sbin/lvm)? If so, the Gentoo startup script /sbin/rc will try to execute it after starting udev to probe for physical volumes, volume groups, and logical volumes. The default configuration of lvm probes _all_ block devices, so this is a probable suspect. You can try adding a filter to /etc/lvm/lvm.conf in this case, like so: filter = [ r|/dev/nbd.*| ] As for whether it should or shouldn't happen, I am not sure. I don't know how common it is to use network block devices...it is definitely a high-end feature. I would guess that anyone using nbd would also be interested in using lvm, so it is probably more useful to have lvm probe these devices if they exist. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Weird Buffer I/O error in dev ndb0
Phill MV wrote: Evertyime I boot up I gett a long string of weird buffer errors shortly after udev starts up; stuff like nbd0: Request when not-ready end_request: I/O error, dev nbd0, sector 4294965120 where ndb0 changes up to ndb12. I still have no clue what dev/ndb0 refers to, but the computer still seems to be running fine. fsck'ing the drives revealed nothing and I might run a memory test later on. (some part of me fears it's my ram, tho, which sounds like it'd make sense. ) Seems like you have the Network Block Device compiled in your Kernel (Device Driver - Block devices) and somebody probes these devices now at bootup. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Weird Buffer I/O error in dev ndb0
Matthias Guede schreef: Phill MV wrote: Evertyime I boot up I gett a long string of weird buffer errors shortly after udev starts up; stuff like nbd0: Request when not-ready end_request: I/O error, dev nbd0, sector 4294965120 where ndb0 changes up to ndb12. I still have no clue what dev/ndb0 refers to, but the computer still seems to be running fine. fsck'ing the drives revealed nothing and I might run a memory test later on. (some part of me fears it's my ram, tho, which sounds like it'd make sense. ) Seems like you have the Network Block Device compiled in your Kernel (Device Driver - Block devices) and somebody probes these devices now at bootup. Yes, I was getting the same errors/warnings; it finally annoyed me so much that I recompiled the kernel without NBD support, since I couldn't find any suggestion that I actually needed it, and all was well after that. Certainly I didn't find that anything which had been working got broke due to the removal-- but that wasn't a big surprise, since the errors/warnings suggested that a function was being probed that did not exist anyway (so I wasn't actually using NBD in the first place, which was what it seemed to be complaining about). HTH, Holly -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Weird Buffer I/O error in dev ndb0
Am Dienstag, den 27.09.2005, 01:31 -0400 schrieb Phill MV: Evertyime I boot up I gett a long string of weird buffer errors shortly after udev starts up; stuff like nbd0: Request when not-ready end_request: I/O error, dev nbd0, sector 4294965120 where ndb0 changes up to ndb12. Same here. Found a post that recommended compiling it as module. Problem solved. I still have no clue what dev/ndb0 refers to, but the computer still seems to be running fine. fsck'ing the drives revealed nothing and I might run a memory test later on. (some part of me fears it's my ram, tho, which sounds like it'd make sense. ) Any ideas? dmesg follows. hif bin # dmesg hda1 hda2 hda3 hda4 hda5 hdb: max request size: 128KiB hdb: 78156288 sectors (40016 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(133) hdb: cache flushes supported hdb: hdb1 hdc: ATAPI 48X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.20 hdd: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33) ide-floppy driver 0.99.newide libata version 1.11 loaded. ieee1394: raw1394: /dev/raw1394 device initialized usbmon: debugs is not available ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 10 PCI: setting IRQ 10 as level-triggered ACPI: PCI Interrupt :00:10.3[D] - Link [LNKE] - GSI 10 (level, low) - IRQ 10 ehci_hcd :00:10.3: VIA Technologies, Inc. USB 2.0 ehci_hcd :00:10.3: new USB bus registered, assigned bus number 1 ehci_hcd :00:10.3: irq 10, io mem 0xe880 ehci_hcd :00:10.3: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004 hub 1-0:1.0: USB hub found hub 1-0:1.0: 6 ports detected ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) USB Universal Host Controller Interface driver v2.2 ACPI: PCI Interrupt :00:10.0[A] - Link [LNKE] - GSI 10 (level, low) - IRQ 10 uhci_hcd :00:10.0: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller uhci_hcd :00:10.0: new USB bus registered, assigned bus number 2 uhci_hcd :00:10.0: irq 10, io base 0xd800 hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected ACPI: PCI Interrupt :00:10.1[B] - Link [LNKE] - GSI 10 (level, low) - IRQ 10 uhci_hcd :00:10.1: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (#2) uhci_hcd :00:10.1: new USB bus registered, assigned bus number 3 uhci_hcd :00:10.1: irq 10, io base 0xd400 hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected ACPI: PCI Interrupt :00:10.2[C] - Link [LNKE] - GSI 10 (level, low) - IRQ 10 uhci_hcd :00:10.2: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (#3) uhci_hcd :00:10.2: new USB bus registered, assigned bus number 4 uhci_hcd :00:10.2: irq 10, io base 0xd000 hub 4-0:1.0: USB hub found hub 4-0:1.0: 2 ports detected usbcore: registered new driver usblp drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver Initializing USB Mass Storage driver... usbcore: registered new driver usb-storage USB Mass Storage support registered. usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.01:USB HID core driver Advanced Linux Sound Architecture Driver Version 1.0.9rc2 (Thu Mar 24 10:33:39 2005 UTC). ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 3 PCI: setting IRQ 3 as level-triggered ACPI: PCI Interrupt :00:11.5[C] - Link [LNKF] - GSI 3 (level, low) - IRQ 3 PCI: Setting latency timer of device :00:11.5 to 64 codec_read: codec 0 is not valid [0x107e5370] codec_read: codec 0 is not valid [0x107e5370] codec_read: codec 0 is not valid [0x107e5370] codec_read: codec 0 is not valid [0x107e5370] ALSA device list: #0: VIA 8235 with AD1980 at 0xe000, irq 3 oprofile: using timer interrupt. NET: Registered protocol family 2 IP: routing cache hash table of 2048 buckets, 16Kbytes TCP established hash table entries: 16384 (order: 5, 131072 bytes) TCP bind hash table entries: 16384 (order: 4, 65536 bytes) TCP: Hash tables configured (established 16384 bind 16384) ip_conntrack version 2.1 (2047 buckets, 16376 max) - 212 bytes per conntrack ip_tables: (C) 2000-2002 Netfilter core team ipt_recent v0.3.1: Stephen Frost [EMAIL PROTECTED]. http://snowman.net/projects/ipt_recent/ arp_tables: (C) 2002 David S. Miller NET: Registered protocol family 1 NET: Registered protocol family 17 ACPI wakeup devices: PCI0 PCI1 USB0 USB1 USB2 SU20 SLAN ACPI: (supports S0 S1 S4 S5) ReiserFS: hda3: found reiserfs format 3.6 with standard journal ReiserFS: hda3: using ordered data mode ReiserFS: hda3: journal params: device hda3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: hda3: checking transaction log (hda3) ReiserFS: hda3: journal-1153: found in header: first_unflushed_offset 6104, last_flushed_trans_id 917135 ReiserFS: hda3: journal-1206: Starting replay from offset 3939069125990360, trans_id 0 ReiserFS: hda3: journal-1299: Setting
Re: [gentoo-user] Weird Buffer I/O error in dev ndb0
That makes me feel much better. On a related note, shouldn't we be filing bug reports, then? Yes, I was getting the same errors/warnings; it finally annoyed me somuch that I recompiled the kernel without NBD support, since I couldn't find any suggestion that I actually needed it, and all was well afterthat. Certainly I didn't find that anything which had been working gotbroke due to the removal-- but that wasn't a big surprise, since the errors/warnings suggested that a function was being probed that did notexist anyway (so I wasn't actually using NBD in the first place, whichwas what it seemed to be complaining about).HTH,Holly-- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Weird Buffer I/O error in dev ndb0
Phill MV schreef: That makes me feel much better. On a related note, shouldn't we be filing bug reports, then? Never occurred to me since it was a PEBKAC (problem existing between keyboard and chair, to save people having to look it up). The only reason NBD was compiled into the kernel was because I put it there, having mysteriously forgotten that I had gotten along fine without it for some time, and having suddenly conceived a conviction that it was some kind of missing link to a network paradise of some sort. Which it may well be, but not for my home network of two puny PCs. I don't know what came over me. And I definitely don't know what kind of a bug 'should' be filed, if I thought one was needed. Holly -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Weird Buffer I/O error in dev ndb0
Well, *something* is trying to access a function that doesnt exist in NDB; whether we know what it does or why, I'm guessing it's a behaviour that shouldn't happen :P. I suppose whatever tries to access NDB has a bug in it... but what would that be?On 27/09/05, Holly Bostick [EMAIL PROTECTED] wrote:Phill MV schreef: That makes me feel much better. On a related note, shouldn't we be filing bug reports, then?Never occurred to me since it was a PEBKAC (problem existing betweenkeyboard and chair, to save people having to look it up). The onlyreason NBD was compiled into the kernel was because I put it there, having mysteriously forgotten that I had gotten along fine without itfor some time, and having suddenly conceived a conviction that it wassome kind of missing link to a network paradise of some sort.Which it may well be, but not for my home network of two puny PCs. I don't know what came over me.And I definitely don't know what kind of a bug 'should' be filed, if Ithought one was needed.Holly--gentoo-user@gentoo.org mailing list
[gentoo-user] Weird Buffer I/O error in dev ndb0
Evertyime I boot up I gett a long string of weird buffer errors shortly after udev starts up; stuff like nbd0: Request when not-ready end_request: I/O error, dev nbd0, sector 4294965120 where ndb0 changes up to ndb12. I still have no clue what dev/ndb0 refers to, but the computer still seems to be running fine. fsck'ing the drives revealed nothing and I might run a memory test later on. (some part of me fears it's my ram, tho, which sounds like it'd make sense. ) Any ideas? dmesg follows. hif bin # dmesg hda1 hda2 hda3 hda4 hda5 hdb: max request size: 128KiB hdb: 78156288 sectors (40016 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(133) hdb: cache flushes supported hdb: hdb1 hdc: ATAPI 48X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.20 hdd: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33) ide-floppy driver 0.99.newide libata version 1.11 loaded. ieee1394: raw1394: /dev/raw1394 device initialized usbmon: debugs is not available ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 10 PCI: setting IRQ 10 as level-triggered ACPI: PCI Interrupt :00:10.3[D] - Link [LNKE] - GSI 10 (level, low) - IRQ 10 ehci_hcd :00:10.3: VIA Technologies, Inc. USB 2.0 ehci_hcd :00:10.3: new USB bus registered, assigned bus number 1 ehci_hcd :00:10.3: irq 10, io mem 0xe880 ehci_hcd :00:10.3: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004 hub 1-0:1.0: USB hub found hub 1-0:1.0: 6 ports detected ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) USB Universal Host Controller Interface driver v2.2 ACPI: PCI Interrupt :00:10.0[A] - Link [LNKE] - GSI 10 (level, low) - IRQ 10 uhci_hcd :00:10.0: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller uhci_hcd :00:10.0: new USB bus registered, assigned bus number 2 uhci_hcd :00:10.0: irq 10, io base 0xd800 hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected ACPI: PCI Interrupt :00:10.1[B] - Link [LNKE] - GSI 10 (level, low) - IRQ 10 uhci_hcd :00:10.1: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (#2) uhci_hcd :00:10.1: new USB bus registered, assigned bus number 3 uhci_hcd :00:10.1: irq 10, io base 0xd400 hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected ACPI: PCI Interrupt :00:10.2[C] - Link [LNKE] - GSI 10 (level, low) - IRQ 10 uhci_hcd :00:10.2: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (#3) uhci_hcd :00:10.2: new USB bus registered, assigned bus number 4 uhci_hcd :00:10.2: irq 10, io base 0xd000 hub 4-0:1.0: USB hub found hub 4-0:1.0: 2 ports detected usbcore: registered new driver usblp drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver Initializing USB Mass Storage driver... usbcore: registered new driver usb-storage USB Mass Storage support registered. usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.01:USB HID core driver Advanced Linux Sound Architecture Driver Version 1.0.9rc2 (Thu Mar 24 10:33:39 2005 UTC). ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 3 PCI: setting IRQ 3 as level-triggered ACPI: PCI Interrupt :00:11.5[C] - Link [LNKF] - GSI 3 (level, low) - IRQ 3 PCI: Setting latency timer of device :00:11.5 to 64 codec_read: codec 0 is not valid [0x107e5370] codec_read: codec 0 is not valid [0x107e5370] codec_read: codec 0 is not valid [0x107e5370] codec_read: codec 0 is not valid [0x107e5370] ALSA device list: #0: VIA 8235 with AD1980 at 0xe000, irq 3 oprofile: using timer interrupt. NET: Registered protocol family 2 IP: routing cache hash table of 2048 buckets, 16Kbytes TCP established hash table entries: 16384 (order: 5, 131072 bytes) TCP bind hash table entries: 16384 (order: 4, 65536 bytes) TCP: Hash tables configured (established 16384 bind 16384) ip_conntrack version 2.1 (2047 buckets, 16376 max) - 212 bytes per conntrack ip_tables: (C) 2000-2002 Netfilter core team ipt_recent v0.3.1: Stephen Frost [EMAIL PROTECTED]. http://snowman.net/projects/ipt_recent/ arp_tables: (C) 2002 David S. Miller NET: Registered protocol family 1 NET: Registered protocol family 17 ACPI wakeup devices: PCI0 PCI1 USB0 USB1 USB2 SU20 SLAN ACPI: (supports S0 S1 S4 S5) ReiserFS: hda3: found reiserfs format 3.6 with standard journal ReiserFS: hda3: using ordered data mode ReiserFS: hda3: journal params: device hda3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: hda3: checking transaction log (hda3) ReiserFS: hda3: journal-1153: found in header: first_unflushed_offset 6104, last_flushed_trans_id 917135 ReiserFS: hda3: journal-1206: Starting replay from offset 3939069125990360, trans_id 0 ReiserFS: hda3: journal-1299: Setting newest_mount_id to 307 ReiserFS: hda3: Using r5 hash to sort names VFS: Mounted root (reiserfs filesystem) readonly. Freeing unused kernel memory: 200k freed nbd0: Request when not-ready end_request: I/O error, dev nbd0, sector 4294965120 Buffer I/O error on device nbd0,
