kernel: attempt to access beyond end of device
sylvai...@etranges-libellules.fr
I hope someone can help me to understand a problem : I get some weird
message in my kern.log , and I wonder how serious it is.
I use :
- Dell Poweredge 1850 with Dell MD3000i iscsi
- Debian Etch 32 bits
- kernel version 2.6.22-4-686 (Debian 2.6.22-6~bpo40+2)
(no...@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian
4.1.1-21)) #1 SMP Tue Feb 12 16:29:32 UTC 2008
- open-iscsi 2.0-869
My Dell Array contains 10To divided by 7 logicial volumes :
80 Gb
80 Gb
1Tb
2Tb
2Tb
2Tb
2Tb
In fact I plugged at 1pm the Dell MD3000i and then I start getting
message a few time before midnight.
I get the same message every 10 min since midnight.
NB : In the kern.log, the first volume of 21Mb isn't a real logical
volume. I thingk it's a communication device for Dell MD3000i that the
open-iscsi driver didn't support, well I guess. But I don't know if it's
linked to my problem.
Thank you
here is a dump of my kern.log :
Apr 17 13:06:51 server02 kernel: Loading iSCSI transport class v2.0-869.
Apr 17 13:06:51 server02 kernel: iscsi: registered transport (tcp)
Apr 17 13:06:51 server02 kernel: scsi32 : iSCSI Initiator over TCP/IP
Apr 17 13:06:51 server02 kernel: scsi 32:0:0:0: Direct-Access
DELL Universal Xport 0670 PQ: 0 ANSI: 5
Apr 17 13:06:51 server02 kernel: sd 32:0:0:0: [sdb] 40960 512-byte
hardware sectors (21 MB)
Apr 17 13:06:51 server02 kernel: sd 32:0:0:0: [sdb] Write Protect is off
Apr 17 13:06:51 server02 kernel: sd 32:0:0:0: [sdb] Mode Sense: 77 00 10 08
Apr 17 13:06:51 server02 kernel: sd 32:0:0:0: [sdb] Write cache:
disabled, read cache: enabled, supports DPO and FUA
Apr 17 13:06:51 server02 kernel: sd 32:0:0:0: [sdb] 40960 512-byte
hardware sectors (21 MB)
Apr 17 13:06:51 server02 kernel: sd 32:0:0:0: [sdb] Write Protect is off
Apr 17 13:06:51 server02 kernel: sd 32:0:0:0: [sdb] Mode Sense: 77 00 10 08
Apr 17 13:06:51 server02 kernel: sd 32:0:0:0: [sdb] Write cache:
disabled, read cache: enabled, supports DPO and FUA
Apr 17 13:06:52 server02 kernel: sdb: unknown partition table
Apr 17 13:06:52 server02 kernel: sd 32:0:0:0: [sdb] Attached SCSI disk
Apr 17 13:06:52 server02 kernel: sd 32:0:0:0: Attached scsi generic sg3
type 0
Apr 17 13:06:52 server02 kernel: scsi 32:0:0:1: Direct-Access
DELL MD3000i 0670 PQ: 0 ANSI: 5
Apr 17 13:06:52 server02 kernel: sd 32:0:0:1: [sdc] 167772160 512-byte
hardware sectors (85899 MB)
Apr 17 13:06:52 server02 kernel: sd 32:0:0:1: [sdc] Write Protect is off
Apr 17 13:06:52 server02 kernel: sd 32:0:0:1: [sdc] Mode Sense: 77 00 10 08
Apr 17 13:06:52 server02 kernel: sd 32:0:0:1: [sdc] Write cache:
enabled, read cache: enabled, supports DPO and FUA
Apr 17 13:06:52 server02 kernel: sd 32:0:0:1: [sdc] 167772160 512-byte
hardware sectors (85899 MB)
Apr 17 13:06:52 server02 kernel: sd 32:0:0:1: [sdc] Write Protect is off
Apr 17 13:06:52 server02 kernel: sd 32:0:0:1: [sdc] Mode Sense: 77 00 10 08
Apr 17 13:06:52 server02 kernel: sd 32:0:0:1: [sdc] Write cache:
enabled, read cache: enabled, supports DPO and FUA
Apr 17 13:06:52 server02 kernel: sdc: sdc1
Apr 17 13:06:52 server02 kernel: sd 32:0:0:1: [sdc] Attached SCSI disk
Apr 17 13:06:52 server02 kernel: sd 32:0:0:1: Attached scsi generic sg4
type 0
Apr 17 13:06:52 server02 kernel: scsi 32:0:0:2: Direct-Access
DELL MD3000i 0670 PQ: 0 ANSI: 5
Apr 17 13:06:52 server02 kernel: sd 32:0:0:2: [sdd] 167772160 512-byte
hardware sectors (85899 MB)
Apr 17 13:06:52 server02 kernel: sd 32:0:0:2: [sdd] Write Protect is off
Apr 17 13:06:52 server02 kernel: sd 32:0:0:2: [sdd] Mode Sense: 77 00 10 08
Apr 17 13:06:52 server02 kernel: sd 32:0:0:2: [sdd] Write cache:
enabled, read cache: enabled, supports DPO and FUA
Apr 17 13:06:52 server02 kernel: sd 32:0:0:2: [sdd] 167772160 512-byte
hardware sectors (85899 MB)
Apr 17 13:06:52 server02 kernel: sd 32:0:0:2: [sdd] Write Protect is off
Apr 17 13:06:52 server02 kernel: sd 32:0:0:2: [sdd] Mode Sense: 77 00 10 08
Apr 17 13:06:52 server02 kernel: sd 32:0:0:2: [sdd] Write cache:
enabled, read cache: enabled, supports DPO and FUA
Apr 17 13:06:52 server02 kernel: sdd: sdd1
Apr 17 13:06:52 server02 kernel: sd 32:0:0:2: [sdd] Attached SCSI disk
Apr 17 13:06:52 server02 kernel: sd 32:0:0:2: Attached scsi generic sg5
type 0
Apr 17 13:06:52 server02 kernel: scsi 32:0:0:3: Direct-Access
DELL MD3000i 0670 PQ: 0 ANSI: 5
Apr 17 13:06:52 server02 kernel: sd 32:0:0:3: [sde] 2147483648 512-byte
hardware sectors (1099512 MB)
Apr 17 13:06:52 server02 kernel: sd 32:0:0:3: [sde] Write Protect is off
Apr 17 13:06:52 server02 kernel: sd 32:0:0:3: [sde] Mode Sense: 77 00 10 08
Apr 17 13:06:52 server02 kernel: sd 32:0:0:3: [sde] Write cache:
enabled, read cache: enabled, supports DPO and FUA
Apr 17 13:06:52 server02 kernel: sd 32:0:0:3: [sde] 2147483648 512-byte
hardware sectors (1099512 MB)
Apr 17 13:06:52 server02 kernel: sd 32:0:0:3: [sde] Write Protect is off
Apr 17 13:06:52 server02 kernel: sd 32:0:0:3: [sde] Mode Sense: 77 00 10 08
Apr 17 13:06:52 server02 kernel: sd 32:0:0:3: [sde] Write cache:
enabled, read cache: enabled, supports DPO and FUA
Apr 17 13:06:52 server02 kernel: sde: sde1
Apr 17 13:06:52 server02 kernel: sd 32:0:0:3: [sde] Attached SCSI disk
Apr 17 13:06:52 server02 kernel: sd 32:0:0:3: Attached scsi generic sg6
type 0
Apr 17 13:06:52 server02 kernel: scsi 32:0:0:4: Direct-Access
DELL MD3000i 0670 PQ: 0 ANSI: 5
Apr 17 13:06:52 server02 kernel: sd 32:0:0:4: [sdf] 4269793280 512-byte
hardware sectors (2186134 MB)
Apr 17 13:06:52 server02 kernel: sd 32:0:0:4: [sdf] Write Protect is off
Apr 17 13:06:52 server02 kernel: sd 32:0:0:4: [sdf] Mode Sense: 77 00 10 08
Apr 17 13:06:52 server02 kernel: sd 32:0:0:4: [sdf] Write cache:
enabled, read cache: enabled, supports DPO and FUA
Apr 17 13:06:52 server02 kernel: sd 32:0:0:4: [sdf] 4269793280 512-byte
hardware sectors (2186134 MB)
Apr 17 13:06:52 server02 kernel: sd 32:0:0:4: [sdf] Write Protect is off
Apr 17 13:06:52 server02 kernel: sd 32:0:0:4: [sdf] Mode Sense: 77 00 10 08
Apr 17 13:06:52 server02 kernel: sd 32:0:0:4: [sdf] Write cache:
enabled, read cache: enabled, supports DPO and FUA
Apr 17 13:06:52 server02 kernel: sdf: sdf1
Apr 17 13:06:52 server02 kernel: sd 32:0:0:4: [sdf] Attached SCSI disk
Apr 17 13:06:52 server02 kernel: sd 32:0:0:4: Attached scsi generic sg7
type 0
Apr 17 13:06:52 server02 kernel: scsi 32:0:0:5: Direct-Access
DELL MD3000i 0670 PQ: 0 ANSI: 5
Apr 17 13:06:52 server02 kernel: sd 32:0:0:5: [sdg] 4269793280 512-byte
hardware sectors (2186134 MB)
Apr 17 13:06:52 server02 kernel: sd 32:0:0:5: [sdg] Write Protect is off
Apr 17 13:06:52 server02 kernel: sd 32:0:0:5: [sdg] Mode Sense: 77 00 10 08
Apr 17 13:06:52 server02 kernel: sd 32:0:0:5: [sdg] Write cache:
enabled, read cache: enabled, supports DPO and FUA
Apr 17 13:06:52 server02 kernel: sd 32:0:0:5: [sdg] 4269793280 512-byte
hardware sectors (2186134 MB)
Apr 17 13:06:52 server02 kernel: sd 32:0:0:5: [sdg] Write Protect is off
Apr 17 13:06:52 server02 kernel: sd 32:0:0:5: [sdg] Mode Sense: 77 00 10 08
Apr 17 13:06:52 server02 kernel: sd 32:0:0:5: [sdg] Write cache:
enabled, read cache: enabled, supports DPO and FUA
Apr 17 13:06:52 server02 kernel: sdg: sdg1
Apr 17 13:06:52 server02 kernel: sd 32:0:0:5: [sdg] Attached SCSI disk
Apr 17 13:06:52 server02 kernel: sd 32:0:0:5: Attached scsi generic sg8
type 0
Apr 17 13:06:52 server02 kernel: scsi 32:0:0:6: Direct-Access
DELL MD3000i 0670 PQ: 0 ANSI: 5
Apr 17 13:06:52 server02 kernel: sd 32:0:0:6: [sdh] 4269793280 512-byte
hardware sectors (2186134 MB)
Apr 17 13:06:52 server02 kernel: sd 32:0:0:6: [sdh] Write Protect is off
Apr 17 13:06:52 server02 kernel: sd 32:0:0:6: [sdh] Mode Sense: 77 00 10 08
Apr 17 13:06:52 server02 kernel: sd 32:0:0:6: [sdh] Write cache:
enabled, read cache: enabled, supports DPO and FUA
Apr 17 13:06:52 server02 kernel: end_request: I/O error, dev sdb, sector 48
Apr 17 13:06:52 server02 kernel: printk: 1 messages suppressed.
Apr 17 13:06:52 server02 kernel: Buffer I/O error on device sdb, logical
block 6
Apr 17 13:06:52 server02 kernel: Buffer I/O error on device sdb, logical
block 7
Apr 17 13:06:52 server02 kernel: Buffer I/O error on device sdb, logical
block 8
Apr 17 13:06:52 server02 kernel: Buffer I/O error on device sdb, logical
block 9
Apr 17 13:06:52 server02 kernel: Buffer I/O error on device sdb, logical
block 10
Apr 17 13:06:52 server02 kernel: Buffer I/O error on device sdb, logical
block 11
Apr 17 13:06:52 server02 kernel: Buffer I/O error on device sdb, logical
block 12
Apr 17 13:06:52 server02 kernel: Buffer I/O error on device sdb, logical
block 13
Apr 17 13:06:52 server02 kernel: Buffer I/O error on device sdb, logical
block 14
Apr 17 13:06:52 server02 kernel: Buffer I/O error on device sdb, logical
block 15
Apr 17 13:06:52 server02 kernel: sd 32:0:0:6: [sdh] 4269793280 512-byte
hardware sectors (2186134 MB)
Apr 17 13:06:52 server02 kernel: sd 32:0:0:6: [sdh] Write Protect is off
Apr 17 13:06:52 server02 kernel: sd 32:0:0:6: [sdh] Mode Sense: 77 00 10 08
Apr 17 13:06:52 server02 kernel: sd 32:0:0:6: [sdh] Write cache:
enabled, read cache: enabled, supports DPO and FUA
Apr 17 13:06:52 server02 kernel: sdh: sdh1
Apr 17 13:06:52 server02 kernel: sd 32:0:0:6: [sdh] Attached SCSI disk
Apr 17 13:06:52 server02 kernel: sd 32:0:0:6: Attached scsi generic sg9
type 0
Apr 17 13:06:52 server02 kernel: scsi 32:0:0:7: Direct-Access
DELL MD3000i 0670 PQ: 0 ANSI: 5
Apr 17 13:06:52 server02 kernel: sd 32:0:0:7: [sdi] 4232355840 512-byte
hardware sectors (2166966 MB)
Apr 17 13:06:52 server02 kernel: sd 32:0:0:7: [sdi] Write Protect is off
Apr 17 13:06:52 server02 kernel: sd 32:0:0:7: [sdi] Mode Sense: 77 00 10 08
Apr 17 13:06:52 server02 kernel: sd 32:0:0:7: [sdi] Write cache:
enabled, read cache: enabled, supports DPO and FUA
Apr 17 13:06:52 server02 kernel: sd 32:0:0:7: [sdi] 4232355840 512-byte
hardware sectors (2166966 MB)
Apr 17 13:06:52 server02 kernel: sd 32:0:0:7: [sdi] Write Protect is off
Apr 17 13:06:52 server02 kernel: sd 32:0:0:7: [sdi] Mode Sense: 77 00 10 08
Apr 17 13:06:52 server02 kernel: sd 32:0:0:7: [sdi] Write cache:
enabled, read cache: enabled, supports DPO and FUA
Apr 17 13:06:52 server02 kernel: sdi: sdi1
Apr 17 13:06:52 server02 kernel: sd 32:0:0:7: [sdi] Attached SCSI disk
Apr 17 13:06:52 server02 kernel: sd 32:0:0:7: Attached scsi generic sg10
type 0
Apr 17 13:06:52 server02 kernel: scsi 32:0:0:8: Direct-Access
DELL MD3000i 0670 PQ: 0 ANSI: 5
Apr 17 13:06:52 server02 kernel: sd 32:0:0:8: [sdj] 20971520 512-byte
hardware sectors (10737 MB)
Apr 17 13:06:52 server02 kernel: sd 32:0:0:8: [sdj] Write Protect is off
Apr 17 13:06:52 server02 kernel: sd 32:0:0:8: [sdj] Mode Sense: 77 00 10 08
Apr 17 13:06:52 server02 kernel: sd 32:0:0:8: [sdj] Write cache:
enabled, read cache: enabled, supports DPO and FUA
Apr 17 13:06:52 server02 kernel: sd 32:0:0:8: [sdj] 20971520 512-byte
hardware sectors (10737 MB)
Apr 17 13:06:52 server02 kernel: sd 32:0:0:8: [sdj] Write Protect is off
Apr 17 13:06:52 server02 kernel: sd 32:0:0:8: [sdj] Mode Sense: 77 00 10 08
Apr 17 13:06:52 server02 kernel: sd 32:0:0:8: [sdj] Write cache:
enabled, read cache: enabled, supports DPO and FUA
Apr 17 13:06:52 server02 kernel: sdj: unknown partition table
Apr 17 13:06:52 server02 kernel: sd 32:0:0:8: [sdj] Attached SCSI disk
Apr 17 13:06:52 server02 kernel: sd 32:0:0:8: Attached scsi generic sg11
type 0
Apr 17 13:07:38 server02 kernel: kjournald starting. Commit interval 5
seconds
Apr 17 13:07:38 server02 kernel: EXT3 FS on sdc1, internal journal
Apr 17 13:07:38 server02 kernel: EXT3-fs: mounted filesystem with
ordered data mode.
Apr 17 13:07:45 server02 kernel: kjournald starting. Commit interval 5
seconds
Apr 17 13:07:45 server02 kernel: EXT3-fs warning: mounting fs with
errors, running e2fsck is recommended
Apr 17 13:07:45 server02 kernel: EXT3 FS on sdd1, internal journal
Apr 17 13:07:45 server02 kernel: EXT3-fs: mounted filesystem with
ordered data mode.
Apr 17 13:07:45 server02 kernel: kjournald starting. Commit interval 5
seconds
Apr 17 13:07:45 server02 kernel: EXT3 FS on sde1, internal journal
Apr 17 13:07:45 server02 kernel: EXT3-fs: mounted filesystem with
ordered data mode.
Apr 17 13:07:45 server02 kernel: kjournald starting. Commit interval 5
seconds
Apr 17 13:07:45 server02 kernel: EXT3 FS on sdf1, internal journal
Apr 17 13:07:45 server02 kernel: EXT3-fs: mounted filesystem with
ordered data mode.
Apr 17 13:07:45 server02 kernel: kjournald starting. Commit interval 5
seconds
Apr 17 13:07:45 server02 kernel: EXT3-fs warning: mounting fs with
errors, running e2fsck is recommended
Apr 17 13:07:45 server02 kernel: EXT3 FS on sdg1, internal journal
Apr 17 13:07:45 server02 kernel: EXT3-fs: mounted filesystem with
ordered data mode.
Apr 17 13:07:46 server02 kernel: kjournald starting. Commit interval 5
seconds
Apr 17 13:07:46 server02 kernel: EXT3 FS on sdh1, internal journal
Apr 17 13:07:46 server02 kernel: EXT3-fs: mounted filesystem with
ordered data mode.
Apr 17 13:07:47 server02 kernel: kjournald starting. Commit interval 5
seconds
Apr 17 13:07:47 server02 kernel: EXT3 FS on sdi1, internal journal
Apr 17 13:07:47 server02 kernel: EXT3-fs: mounted filesystem with
ordered data mode.
Apr 17 13:11:36 server02 kernel: kjournald starting. Commit interval 5
seconds
Apr 17 13:11:36 server02 kernel: EXT3 FS on sdi1, internal journal
Apr 17 13:11:36 server02 kernel: EXT3-fs: mounted filesystem with
ordered data mode.
Apr 17 13:12:28 server02 kernel: kjournald starting. Commit interval 5
seconds
Apr 17 13:12:28 server02 kernel: EXT3 FS on sdi1, internal journal
Apr 17 13:12:28 server02 kernel: EXT3-fs: mounted filesystem with
ordered data mode.
Apr 17 23:19:01 server02 kernel: attempt to access beyond end of device
Apr 17 23:19:01 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 17 23:19:01 server02 kernel: attempt to access beyond end of device
Apr 17 23:19:01 server02 kernel: sdg1: rw=0, want=6716155992,
limit=4269787767
Apr 17 23:19:01 server02 kernel: attempt to access beyond end of device
Apr 17 23:19:01 server02 kernel: sdg1: rw=0, want=6467719256,
limit=4269787767
Apr 17 23:19:01 server02 kernel: attempt to access beyond end of device
Apr 17 23:19:01 server02 kernel: sdg1: rw=0, want=4321771976,
limit=4269787767
Apr 17 23:19:01 server02 kernel: attempt to access beyond end of device
Apr 17 23:19:01 server02 kernel: sdg1: rw=0, want=6593550736,
limit=4269787767
Apr 17 23:19:01 server02 kernel: attempt to access beyond end of device
Apr 17 23:19:01 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 17 23:19:01 server02 kernel: attempt to access beyond end of device
Apr 17 23:19:01 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 17 23:45:19 server02 kernel: attempt to access beyond end of device
Apr 17 23:45:19 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 17 23:45:19 server02 kernel: attempt to access beyond end of device
Apr 17 23:45:19 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 18 00:01:36 server02 kernel: attempt to access beyond end of device
Apr 18 00:01:36 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 18 00:01:36 server02 kernel: attempt to access beyond end of device
Apr 18 00:01:36 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 18 00:01:43 server02 kernel: attempt to access beyond end of device
Apr 18 00:01:43 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 18 00:01:43 server02 kernel: attempt to access beyond end of device
Apr 18 00:01:43 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 18 00:10:29 server02 kernel: attempt to access beyond end of device
Apr 18 00:10:29 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
(...)
Apr 18 11:00:28 server02 kernel: attempt to access beyond end of device
Apr 18 11:00:28 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 18 11:00:28 server02 kernel: attempt to access beyond end of device
Apr 18 11:00:28 server02 kernel: sdg1: rw=0, want=6716155992,
limit=4269787767
Apr 18 11:00:28 server02 kernel: attempt to access beyond end of device
Apr 18 11:00:28 server02 kernel: sdg1: rw=0, want=6467719256,
limit=4269787767
Apr 18 11:00:28 server02 kernel: attempt to access beyond end of device
Apr 18 11:00:28 server02 kernel: sdg1: rw=0, want=4321771976,
limit=4269787767
Apr 18 11:00:28 server02 kernel: attempt to access beyond end of device
Apr 18 11:00:28 server02 kernel: sdg1: rw=0, want=6593550736,
limit=4269787767
Apr 18 11:00:28 server02 kernel: attempt to access beyond end of device
Apr 18 11:00:28 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 18 11:00:28 server02 kernel: attempt to access beyond end of device
Apr 18 11:00:28 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 18 11:00:34 server02 kernel: attempt to access beyond end of device
Apr 18 11:00:34 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 18 11:00:34 server02 kernel: attempt to access beyond end of device
Apr 18 11:00:34 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 18 11:10:27 server02 kernel: attempt to access beyond end of device
Apr 18 11:10:27 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 18 11:10:27 server02 kernel: attempt to access beyond end of device
Apr 18 11:10:27 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 18 11:10:34 server02 kernel: attempt to access beyond end of device
Apr 18 11:10:34 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 18 11:10:34 server02 kernel: attempt to access beyond end of device
Apr 18 11:10:34 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 18 11:20:31 server02 kernel: attempt to access beyond end of device
Apr 18 11:20:31 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 18 11:20:31 server02 kernel: attempt to access beyond end of device
Apr 18 11:20:31 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 18 11:20:36 server02 kernel: attempt to access beyond end of device
Apr 18 11:20:36 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
Apr 18 11:20:36 server02 kernel: attempt to access beyond end of device
Apr 18 11:20:36 server02 kernel: sdg1: rw=0, want=15977179552,
limit=4269787767
--
Sylvain DAVID / administrateur réseau
adr : Etranges Libellules
.~. 17 Rue des Archers
/v\ 69002 LYON
/(°)\ tel : 04 72 40 24 72
^^-^^ fax : 04 72 40 27 19
sylvai...@etranges-libellules.fr
It's a pure file system layer error, so now I'm fsck'ing the file system
...Hope I won't loose a large amount of data.
Really sorry, my question was a noob one.
And thank you for your great job open-iscsi team.
Sylvain DAVID / Administrateur réseaux
adr : Etranges Libellules
.~. 17 Rue des Archers
/v\ 69002 LYON
/(°)\ tel : 04 72 40 24 72
^^-^^ fax : 04 72 40 27 19
sylvai...@etranges-libellules.fr a écrit :
Konrad Rzeszutek
> message a few time before midnight.
> I get the same message every 10 min since midnight.
It looks as there is some applications that is trying to access
sectors above what the device has. Did you look through your cronjobs
to see what is run?
>
> NB : In the kern.log, the first volume of 21Mb isn't a real logical
> volume. I thingk it's a communication device for Dell MD3000i that the
> open-iscsi driver didn't support, well I guess. But I don't know if it's
> linked to my problem.
If you are using multipath then this block device would be black-listed.
sylvai...@etranges-libellules.fr
Konrad Rzeszutek a écrit :
>> In fact I plugged at 1pm the Dell MD3000i and then I start getting
>> message a few time before midnight.
>> I get the same message every 10 min since midnight.
>>
>
> It looks as there is some applications that is trying to access
> sectors above what the device has. Did you look through your cronjobs
> to see what is run?
>
>
with another server. When the script parsed the corrupted files the logs
said there were I/O error with the SAN.
My problem wasn't on iscsi layer but on the file system layer and a
e2fsck resolve it properly.
You probably wants to know why I got some errors on the file system in
my iscsi SAN. It's my fault : before to plug the SAN on the production
server, it was plugged on the test server. And this test server freezed
because of a bad memory chip issue (now I have changed the bad chip and
memtest the new one to prevent future errors) and that happened of
course during a iscsi session was opened.
When I rebooted the server, I thinked that recovering the journal of
ext3 file system was sufficient, and it wasn't. Shame on me, I didn't
tell this fact in the mail before, and I can't explain why I didn't
realize before that it was the source of this problem. It' so logical.
>> NB : In the kern.log, the first volume of 21Mb isn't a real logical
>> volume. I thingk it's a communication device for Dell MD3000i that the
>> open-iscsi driver didn't support, well I guess. But I don't know if it's
>> linked to my problem.
>>
>
> If you are using multipath then this block device would be black-listed.
>
>
I don't use multipath for the while, but I will remember.
Thank you!
>
> Sylvain DAVID / Administrateur réseaux
>