On Fri, 07 Apr 2017 00:18:45 +0200, L A Walsh wrote:
Someone else posted problems on the opensuse list about the new crc option, a few days ago on Leap 42.2, but they didn't give enough detail to tell if it was the same bug.
If anyone has a problem with the last update kernel, please try KOTD available in OBS Kernel:openSUSE-42.2 repo, which is the build from the latest git snapshot. http://download.opensuse.org/repositories/Kernel:/openSUSE-42.2/ And, don't hesitate to report to openSUSE bugzilla. (But the test with KOTD will be asked in anyway there :) If the reported problem is serious, we can re-submit the newer update kernel quickly, just submitting from the working KOTD. thanks, Takashi
-linda
-------- Original Message -------- Subject: XFS and CRC on Leap 42.2 Date: Sun, 2 Apr 2017 15:56:05 -0400 From: Ciro Iriarte To: OpenSuse List
Hi!, can anyone comment on XFS stability on Leap 42.2 using crc=1?. I've read that crc=1 should be the new default. I created a XFS filesystem with explicit crc=1.
Everything was working fine until I used that filesystem as a NFS repository for ESXi, tried to move some VMs to it and had a complete hang, hours later the filesystem went to read only mode.
Trying to repair the FS I get CRC errors on the pending changelog. I can purge the log, as the entries reference the directories of the VMs I tried to move but I'm a little worried about keeping it like that. I've just moved from BTRFS trying to avoid this issues :/
Regards,
-- Ciro Iriarte http://iriarte.it
-- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org