Date: Sat, 5 Aug 2017 22:08:54 +0500 From: "Eugene M. Zheganin" <emz@norma.perm.ru> To: freebsd-stable@FreeBSD.org Cc: freebsd-fs@freebsd.org Subject: a strange and terrible saga of the cursed iSCSI ZFS SAN Message-ID: <1bd10b1e-0583-6f44-297e-3147f6daddc5@norma.perm.ru>
next in thread | raw e-mail | index | archive | help
Hi,
I got a problem that I cannot solve just by myself. I have a iSCSI zfs
SAN system that crashes, corrupting it's data. I'll be short, and try to
describe it's genesis shortly:
1) autumn 2016, SAN is set up, supermicro server, external JBOD, sandisk
ssds, several redundant pools, FreeBSD 11.x (probably release, don't
really remember - see below).
2) this is working just fine until early spring 2017
3) system starts to crash (various panics):
panic: general protection fault
panic: page fault
panic: Solaris(panic): zfs: allocating allocated
segment(offset=6599069589504 size=81920)
panic: page fault
panic: page fault
panic: Solaris(panic): zfs: allocating allocated
segment(offset=8245779054592 size=8192)
panic: page fault
panic: page fault
panic: page fault
panic: Solaris(panic): zfs: allocating allocated
segment(offset=1792100934656 size=46080)
4) we memtested it immidiately, no problems found.
5) we switch sandisks to toshibas, we switch also the server to an
identical one, JBOD to an identical one, leaving same cables.
6) crashes don't stop.
7) we found that field engineers physically damaged (sic!) the SATA
cables (main one and spare ones), and that 90% of the disks show ICRC
SMART errors.
8) we replaced the cable (brand new HP one).
9) ATA SMART errors stopped increasing.
10) crashes continue.
11) we decided that probably when ZFS was moved over damaged cables
between JBODs it was somehow damaged too, so now it's panicking because
of that. so we wiped the data completely, reinitialized the SAN system
and put it back into the production. we even dd'ed each disk with zeroes
(!) - just in case. Important note: the data was imported using zfs send
from another, stable system that is runing in production in another DC.
12) today we got another panic.
btw the pools look now like this:
# zpool status -v
pool: data
state: ONLINE
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise restore the
entire pool from backup.
see: http://illumos.org/msg/ZFS-8000-8A
scan: none requested
config:
NAME STATE READ WRITE CKSUM
data ONLINE 0 0 62
raidz1-0 ONLINE 0 0 0
da2 ONLINE 0 0 0
da3 ONLINE 0 0 0
da4 ONLINE 0 0 0
da5 ONLINE 0 0 0
da6 ONLINE 0 0 0
raidz1-1 ONLINE 0 0 0
da7 ONLINE 0 0 0
da8 ONLINE 0 0 0
da9 ONLINE 0 0 0
da10 ONLINE 0 0 0
da11 ONLINE 0 0 0
raidz1-2 ONLINE 0 0 62
da12 ONLINE 0 0 0
da13 ONLINE 0 0 0
da14 ONLINE 0 0 0
da15 ONLINE 0 0 0
da16 ONLINE 0 0 0
errors: Permanent errors have been detected in the following files:
data/userdata/worker208:<0x1>
pool: userdata
state: ONLINE
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise restore the
entire pool from backup.
see: http://illumos.org/msg/ZFS-8000-8A
scan: none requested
config:
NAME STATE READ WRITE CKSUM
userdata ONLINE 0 0 216K
mirror-0 ONLINE 0 0 432K
gpt/userdata0 ONLINE 0 0 432K
gpt/userdata1 ONLINE 0 0 432K
errors: Permanent errors have been detected in the following files:
userdata/worker36:<0x1>
userdata/worker30:<0x1>
userdata/worker31:<0x1>
userdata/worker35:<0x1>
12) somewhere between p.5 and p.10 the pool became deduplicated (not
directly connected to the problem, just for production reasons).
So, concluding: we had bad hardware, we replaced EACH piece (server,
adapter, JBOD, cable, disks), and crashes just don't stop. We have 5
another iSCSI SAN systems, almost fully identical that don't crash.
Crashes on this particular system began when it was running same set of
versions that stable systems.
So, besides calling an exorcist, I would like to hear what other options
do I have, I really would.
And I want to also ask - what happens when the system's memory isn't
enough for deduplication - does it crash, or does the problem of
mounting the pool appear, like some articles mention ?
This message could been encumbered by junky data like the exact FreeBSD
releases we ran (asuuming it's normal for some 11.x revisions to crash
and damage the data, and some - not, which I believe it's a nonsense),
by the pool configurations and disk lists (assuming the same - that you
can provoque data loss by some redundant pool configurations - not
considering raidz with more than 5 disks - which I believe is not true),
and so on. but I decided not to include this until requested. And as I
also said, we have 5 another SAN systems running similar/identical
configurations without major problems.
Thanks.
Eugene.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1bd10b1e-0583-6f44-297e-3147f6daddc5>