I don't remember, this error appeared immediately after create file system or after
created many files. But after I add parameter vmalloc to grub2.conf problem was resolved.
On Thu, Jul 03, 2014 at 03:24:37PM -0600, Chris Murphy wrote:
On Jul 3, 2014, at 10:49 AM, Roman Kravets <admin(a)softded.net> wrote:
> On Wed, Jul 02, 2014 at 02:50:10PM -0600, Chris Murphy wrote:
>> On Jun 30, 2014, at 9:44 PM, Roman Kravets <admin(a)softded.net> wrote:
>>> [softded@softded ~]$ mount | grep xfs
>>> /dev/mapper/encrypt-store on /mnt/store type xfs
>>> [softded@softded ~]$ xfs_info /dev/mapper/encrypt-store
>>> meta-data=/dev/mapper/encrypt-store isize=256 agcount=16, agsize=2440064
>>> = sectsz=512 attr=2, projid32bit=0
>>> = crc=0
>>> data = bsize=4096 blocks=39041024, imaxpct=25
>>> = sunit=128 swidth=256 blks
>>> naming =version 2 bsize=4096 ascii-ci=0 ftype=0
>>> log =internal bsize=4096 blocks=19064, version=2
>>> = sectsz=512 sunit=8 blks, lazy-count=1
>>> realtime =none extsz=4096 blocks=0, rtextents=0
>> 149GiB file system, is that correct?
>> Is this filesystem on hardware or software raid?
> Dear Chris,
> Yes. It is correct.
> I have software raid10 witch 4x80GB HDD.
> I store on it raid my mail archive.
Ok well everything there looks normal. I'd still consider posting the experience to
the XFS list, checking the XFS FAQ for the information to include in the submission. The
fact you get this on fs mount and it inhibits a normal mount is pretty weird. It's not
like it's a big file system either, but maybe it has something to do with 10 million
files vs the size of the file system.