Re: Unmountable XFS file system after runnig stress-ng

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Unmountable XFS file system after runnig stress-ng
From: Paul Menzel <pmenzel@xxxxxxxxxxxxx>
Date: Sat, 27 Jul 2019 23:39:18 +0200
Cc: linux-xfs@xxxxxxxxxxxxxxx
In-reply-to: <CA+VdTb8ZPLi0Eiq9SEhem4aEjWJ3rCn+NQ_vZrpc9mXo_WuDDQ@mail.gmail.com>
References: <b92674c4-488e-15ec-2052-eb69e4f80b7e@molgen.mpg.de> <20190727002439.GS30113@42.do-not-panic.com> <CA+VdTb8ZPLi0Eiq9SEhem4aEjWJ3rCn+NQ_vZrpc9mXo_WuDDQ@mail.gmail.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0

Dear Rob,


On 27.07.19 13:34, Rob Townley wrote:

Is there ECC RAM in this PC?

“Corruption of in-memory data detected.  Shutting down filesystem“


Yes, there is ECC memory in that system.


Kind regards,

Paul

References:
- Unmountable XFS file system after runnig stress-ng
  - From: Paul Menzel
- Re: Unmountable XFS file system after runnig stress-ng
  - From: Luis Chamberlain

Prev by Date: Re: lift the xfs writepage code into iomap v3
Next by Date: Re: [PATCH 0/4] xfs: fixes and new tests for bulkstat v5
Previous by thread: Re: Unmountable XFS file system after runnig stress-ng
Next by thread: [PATCH v2] xfs: fix stack contents leakage in the v1 inumber ioctls
Index(es):
- Date
- Thread

[Index of Archives] [XFS Filesystem Development (older mail)] [Linux Filesystem Development] [Linux Audio Users] [Yosemite Trails] [Linux Kernel] [Linux RAID] [Linux SCSI]

Powered by Linux