Date: Thu, 29 Aug 2019 10:37:28 +0200 From: Julien Cigar <julien@perdition.city> To: Albert Shih <Albert.Shih@obspm.fr> Cc: freebsd-questions@freebsd.org Subject: Re: Verry serious problem with ZFS & 12.0 Message-ID: <20190829083727.GC38457@home.lan> In-Reply-To: <20190828224547.GA1557@io.chezmoi.fr> References: <20190828224547.GA1557@io.chezmoi.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Thu, Aug 29, 2019 at 12:45:47AM +0200, Albert Shih wrote: > Hi > > After update 4 servers from 11.2 to 12.0 without any problem, wait few > weeks to see if everything work well, and it did. I just upgrade my mail > server. > > During the upgrade I also upgrade all firmware for the hardware. > > And now I got a very serious issue with my server. > > Configuration : > > Dell PowerEdge R740Xd with H730P, 192 Go Ram, 2 SAS mechanical disk for the system, > 2 SSD (in a zfs pool) for the mail index (cyrus), and 28 mechanical disk > (in a second zfs pool) for the mailbox. > > The problem: > > After running few days the zfs pool with the 2 SSD are not responding. > > The system are perfectly working. > > The second zpool (mechanical disk) are perfectly working. > > I got zero log, zero message in the console or in dmesg. > > The arc_size are correct, it's around 70-75 %. > > The moment the zfs pool become not responding are random, not related to > any activity (human or cron). > > The only option I pass for the kernel related to ZFS are vfs.zfs.min_auto_ashift=12 and > vfs.zfs.prefetch_disable=1. Without the second one the system no > responding (under 11.2) when the server send (through zfs send) the data to another > server. > > After the first problem I make a zfs upgrade, thinking maybe that's the > problem so I'm not sure I can downgrade to 11.2 (and 11.2 are EOL) > > In your opinion : > > 1/ What should I do to try to find the problem ? > > 2/ Do you think that's a hardware/firmware problem or FreeBSD problem, > the point is the second zpool are working perfectly so I'm thinking at > some firmware/hardware/compatibility problem. > > > Regards. looks like PR 236480 see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236480 > > > -- > Albert SHIH > DIO bâtiment 15 > Observatoire de Paris > Heure local/Local time: > Thu 29 Aug 2019 12:26:55 AM CEST > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" -- Julien Cigar Belgian Biodiversity Platform (http://www.biodiversity.be) PGP fingerprint: EEF9 F697 4B68 D275 7B11 6A25 B2BB 3710 A204 23C0 No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEE7vn2l0to0nV7EWolsrs3EKIEI8AFAl1njsMACgkQsrs3EKIE I8D21A//V4v3BeceoWUHM5KsYdP+tElxNVoE4npCVzXj5Vjgwy/Z+ogWEw5wB3Ze ALTN3YLbv1wQBPqs5zII53JHoFTzV2U0G9/rZrxAlMEmUz6xDAD2StirWblOLfXe tW4HMvOQCJszaOoYX9giaziLbzx3Ca7fOa9HYWK074MdPmMcZYGdH4Qx1KTne7nC J6+SgLB4FbBjqfvS7DsfONW1OSQcoIdf3gjiA3cKaIlZhxCQzBraJaqvYkqxpRY/ k/lJMhiZv4B6mljvngCanWm3C814g9yjU0nOy58iKFrT82M981K09jQ1m7zYqCxd IYmXcjiMZ6GA46uSBJvpuQWdwpoGVpEDiFDo43XdebNBAa3LUwJ+bHgDv64tfVDR sbvSRt+sjOhjkWPP2aWFtQdM+jvClozPdRVUDHarPqdygMp1op/upUU8LEoWbqlk /1SNAa4dk7HRIxgL6j2e47gCgqIlvUQbfEnVA7mr0TsEhpmpx2ECbvBU1vDPP0W9 mYsMQe2aFADNJxoUoToGD5xzz6s2Z2q5gHdxToM6PoTEi8SkVE+R69MVD/h6PmuE TiDezOzOLhyAgu8w0CE+tgVuvFtVaxN/IjoLFH/8861cqIts0msMwpoo/QREKeha DW3IzPsQhNtSS5pMQFRQiwi7me9mmVh49qn/TvJJ5TD/IQHWX/0= =gLLp -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190829083727.GC38457>