| To: | Emmanuel Florac <eflorac@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Weird behaviour of mkfs.xfs |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Sat, 26 Mar 2016 09:36:42 -0700 |
| Cc: | "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20160326154619.3649ebdf@xxxxxxxxxxxxxxxxxxxx> |
| References: | <20160326145037.3b5c6302@xxxxxxxxxxxxxxxxxxxx> <20160326154619.3649ebdf@xxxxxxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.24 (2015-08-30) |
On Sat, Mar 26, 2016 at 03:46:19PM +0100, Emmanuel Florac wrote: > Actually I was too impatient; it finally ended avec 30 minutes of > burning bits to the flash. I don't understand the behaviour, though. > I'm used to mkfs.xfs making its magic extremely quickly, even on > humongous devices. Here it's a very fast array of only 3.2 TB... Trey doing a mkfs.xfs -K, without that it diascards the whole device. I've seen some NVMe device misbehaving under discard storms, up to the point of resetting the controller.. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Weird behaviour of mkfs.xfs, Emmanuel Florac |
|---|---|
| Next by Date: | Re: [PATCH 5/5] dax: handle media errors in dax_do_io, hch@xxxxxxxxxxxxx |
| Previous by Thread: | Re: Weird behaviour of mkfs.xfs, Emmanuel Florac |
| Next by Thread: | Re: Weird behaviour of mkfs.xfs, Emmanuel Florac |
| Indexes: | [Date] [Thread] [Top] [All Lists] |