[softded@softded ~]$ mount | grep xfs /dev/mapper/encrypt-store on /mnt/store type xfs (rw,noatime,nodiratime,attr2,inode64,sunit=1024,swidth=2048,noquota)
[softded@softded ~]$ xfs_info /dev/mapper/encrypt-store meta-data=/dev/mapper/encrypt-store isize=256 agcount=16, agsize=2440064 blks = 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
On Mon, Jun 30, 2014 at 02:00:26PM -0600, Chris Murphy wrote:
On Jun 30, 2014, at 9:51 AM, Roman Kravets admin@softded.net wrote:
Dear Chris,
After I added parameter vmalloc=256M to my grub2.conf problem resolved.
I don't know need will add it parameter to default grub2.conf or not, but when I used my XFS partition with default vmalloc I did't see problem. It's just interested for me and therefore I asked Community.
It sounds like a bug somewhere. What are the mount options and fs info for this XFS file system?
mount | grep xfs xfs_info <dev>
Chris Murphy
users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org