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 wrote:
> >
On Jul 3, 2014, at 10:49 AM, Roman Kravets wrote:
>
> On Wed, Jul 02, 2014 at 02:50:10PM -0600, Chris Murphy wrote:
>>
>> On Jun 30, 2014, at 9:44 PM, Roman Kravets wrote:
>>
>>> [softded@softded ~]$ mount | grep xfs
>>> /dev/mapper/encrypt-store on /mnt/store type xfs
>>> (rw,noatime,nodira
Dear Chris,
Yes. It is correct.
I have software raid10 witch 4x80GB HDD.
I store on it raid my mail archive.
On Wed, Jul 02, 2014 at 02:50:10PM -0600, Chris Murphy wrote:
>
> On Jun 30, 2014, at 9:44 PM, Roman Kravets wrote:
>
> > [softded@softded ~]$ mount | grep xfs
> > /dev/mapper/encrypt
On Jun 30, 2014, at 9:44 PM, Roman Kravets wrote:
> [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/
[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=256agcount=16, agsize=2440064 blks
Allegedly, on or about 30 June 2014, Rick Stevens sent:
> You mean there is such a thing as a "graceful" failure? Wow! Gotta
> tell my boss about that!
Ungraceful failure: Instant hard crash with complete lock-up!
Graceful failure: You get an error message, first, but you're still
screwed.
;-p
On Jun 30, 2014, at 9:51 AM, Roman Kravets 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.
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.
On
Dear Roger and Heinz,
Thank you for you answer!
I added it parameter to grub2.conf and problem resolved.
On Sat, Jun 28, 2014 at 11:55:39AM -0500, Roger Heflin wrote:
> On Sat, Jun 28, 2014 at 10:41 AM, Heinz Diehl wrote:
> > On 27.06.2014, Roman Kravets wrote:
> >
> >> Jun 27 11:14:38 softded
On 06/30/2014 10:10 AM, Chris Murphy issued this missive:
...or non-graceful failures as possible.
You mean there is such a thing as a "graceful" failure? Wow! Gotta tell
my boss about that!
(tongue planted firmly in cheek)
-
On Jun 27, 2014, at 2:40 AM, Roman Kravets wrote:
> Hello!
>
> When I mount my disk with XFS I saw error in dmesg:
>
> Jun 27 11:14:38 softded kernel: XFS (dm-4): xfs_buf_get_uncached: failed to
> map pages
> Jun 27 11:14:38 softded kernel: vmap allocation for size 1048576 failed: use
> vmal
On Sat, Jun 28, 2014 at 10:41 AM, Heinz Diehl wrote:
> On 27.06.2014, Roman Kravets wrote:
>
>> Jun 27 11:14:38 softded kernel: vmap allocation for size 1048576 failed: use
>> vmalloc= to increase size.
>> What is it meen "use vmalloc= to increase size"? When can I change it
>> parameter?
>
> It
On 27.06.2014, Roman Kravets wrote:
> Jun 27 11:14:38 softded kernel: vmap allocation for size 1048576 failed: use
> vmalloc= to increase size.
> What is it meen "use vmalloc= to increase size"? When can I change it
> parameter?
It is a kernel boot parameter, which you can add manually be edit
Hello!
When I mount my disk with XFS I saw error in dmesg:
Jun 27 11:14:38 softded kernel: XFS (dm-4): xfs_buf_get_uncached: failed to map
pages
Jun 27 11:14:38 softded kernel: vmap allocation for size 1048576 failed: use
vmalloc= to increase size.
Jun 27 11:14:38 softded kernel: vmap allocatio
14 matches
Mail list logo
