|Subject:||Re: ENOSPC and filesystem shutdowns|
|From:||Bernard Chan <bernard@xxxxxxxxxxxxx>|
|Date:||Thu, 8 Sep 2011 19:09:55 +0800|
|Cc:||Christoph Hellwig <hch@xxxxxxxxxxxxx>|
Hi Christoph and everybody else,
Thanks so much for your response.
We are running this on a customized CentOS image on AWS and thus had a different kernel version. We learned from the image vendors that these are based on CentOS and indeed they seem to be, although we do not know the exact CentOS versions on which those images were based.
We switched to another image that offers a newer kernel version (220.127.116.11), and re-mounted the LVM with XFS volumes. Earlier on we performed xfs_repair and did not find any problems, and fragmentation was found to be low. We retried those mkdir operations that previously resulted in ENOSPC which in turn shut down the XFS. There is no longer any XFS shutdown now and the same operations are successful. We feel curious and do not quite understand why, and we haven't enabled inode64 either with the new setup and remain on a 32-bit architecture. Essentially we only changed the kernel and a slightly different 32-bit image.
So should we bother with inode64 and 64-bit servers with NFS4, and should we anticipate any other issues running on this setup with a 4TB volume without enabling inode64?
Thanks so much for any possible insights.
On Mon, Sep 5, 2011 at 3:47 PM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote:
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||XFS: Observed Crash followed by deadlock of khubd/sync/XFS, Amit Sahrawat|
|Next by Date:||Re: [Drbd-dev] [3.1-rc4] XFS+DRBD hangs, Lars Ellenberg|
|Previous by Thread:||Re: ENOSPC and filesystem shutdowns, Christoph Hellwig|
|Next by Thread:||Re: ENOSPC and filesystem shutdowns, Michael Monnerie|
|Indexes:||[Date] [Thread] [Top] [All Lists]|