zfs discuss - Jun 2009 - [caiman-discuss] Can not delete swap on AI sparc

Hi Richard,


Richard Robinson wrote:
> I should add that I also used truss and saw the same ENOMEM error.  I am on
a 4Gb system with swap -l reporting
>
> swapfile             dev  swaplo blocks   free
> /dev/zvol/dsk/rpool/swap 181,1       8 4194296 4194296
>
> and I was trying to follow the directions for increasing swap here:
>
http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide#Resizing_ZFS_Swap_and_Dump_Devices
if I understand correctly, in your case the failure
occurs when you try to increase swap size by means
of ''zfs set volsize'' command ?
CCing ZFS team.

Thank you,
Jan

Hi Richard,

I ran into some quirks resizing swap last week.

If you are seeing out of space when trying to remove a swap area, then a 
reboot clear this up. I think the bugs are already filed, but I would
like to see your scenario as well.

Can you restate your steps?

Thanks,

Cindy


Jan Damborsky wrote:
> Hi Richard,
> 
> 
> Richard Robinson wrote:
> 
>> I should add that I also used truss and saw the same ENOMEM error.  I 
>> am on a 4Gb system with swap -l reporting
>>
>> swapfile             dev  swaplo blocks   free
>> /dev/zvol/dsk/rpool/swap 181,1       8 4194296 4194296
>>
>> and I was trying to follow the directions for increasing swap here:
>>
http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide#Resizing_ZFS_Swap_and_Dump_Devices
>>
> 
> 
> if I understand correctly, in your case the failure
> occurs when you try to increase swap size by means
> of ''zfs set volsize'' command ?
> CCing ZFS team.
> 
> Thank you,
> Jan
> 
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

hi Jan (and all)

My failure was when running

# swap -d /dev/zvol/dsk/rpool/swap

I saw this in my truss output.

uadmin(16, 3, -2748781172232)            Err#12 ENOMEM


Another email recommended that I reboot and try again and that seems to 
have worked.  I was actually running Solaris 10 u7 with a ZFS root FS 
and not Open Solaris.

It looks like it is CR 6576458 (to me).

thanks,
Richard


Jan Damborsky wrote:
> Hi Richard,
>
>
> Richard Robinson wrote:
>> I should add that I also used truss and saw the same ENOMEM error.  I 
>> am on a 4Gb system with swap -l reporting
>>
>> swapfile             dev  swaplo blocks   free
>> /dev/zvol/dsk/rpool/swap 181,1       8 4194296 4194296
>>
>> and I was trying to follow the directions for increasing swap here:
>>
http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide#Resizing_ZFS_Swap_and_Dump_Devices
>>
>
> if I understand correctly, in your case the failure
> occurs when you try to increase swap size by means
> of ''zfs set volsize'' command ?
> CCing ZFS team.
>
> Thank you,
> Jan
>
-- 

    * Richard Robinson
    * Engineer, SWTSC -- Sun Secure Global Desktop
    * Send me an email. <mailto:Richard.Robinson at sun.com>
    * <mailto:Richard.Robinson at sun.com> Have you gathered all of the
      data to speed your case along? <mailto:Richard.Robinson at sun.com>
    * <mailto:Richard.Robinson at sun.com> Sun Gathering Debug Data for
Sun
      Secure Global Desktop - Sun Microsystems
      <http://docs.sun.com/app/docs/doc/820-4798/6ng85les2?a=view>

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20090608/b5dff850/attachment.html>

>hi Jan (and all)
>
>My failure was when running
>
># swap -d /dev/zvol/dsk/rpool/swap
>
>I saw this in my truss output.
>
>uadmin(16, 3, -2748781172232)            Err#12 ENOMEM
>
That sounds like "too much memory in use: can''t remove swap".

Casper

Casper.Dik at Sun.COM wrote:
>
>> hi Jan (and all)
>>
>> My failure was when running
>>
>> # swap -d /dev/zvol/dsk/rpool/swap
>>
>> I saw this in my truss output.
>>
>> uadmin(16, 3, -2748781172232)            Err#12 ENOMEM
>>
>
> That sounds like "too much memory in use: can''t remove
swap".
It seems it also happens in situations when only small portion
of swap is in use and there is enough free physical memory
available to release swap device.
I am not sure how memory management works, I was thinking
that releasing swap device should be feasible in such
situations, but maybe this is the limitation of memory management
itself.

Thank you,
Jan