Displaying 5 results from an estimated 5 matches for "vmem_free".
2007 May 02
41
gzip compression throttles system?
I just had a quick play with gzip compression on a filesystem and the
result was the machine grinding to a halt while copying some large
(.wav) files to it from another filesystem in the same pool.
The system became very unresponsive, taking several seconds to echo
keystrokes. The box is a maxed out AMD QuadFX, so it should have plenty
of grunt for this.
Comments?
Ian
2012 Jun 06
24
Occasional storm of xcalls on segkmem_zio_free
...:::xcalls {@[stack()]=count();}''
unix`xc_call+0x46
unix`hat_tlb_inval+0x283
unix`x86pte_inval+0xaa
unix`hat_pte_unmap+0xed
unix`hat_unload_callback+0x193
unix`hat_unload+0x41
unix`segkmem_free_vn+0x6f
unix`segkmem_zio_free+0x27
genunix`vmem_xfree+0x104
genunix`vmem_free+0x29
genunix`kmem_slab_destroy+0x87
genunix`kmem_slab_free+0x2bb
genunix`kmem_magazine_destroy+0x39a
genunix`kmem_depot_ws_reap+0x66
genunix`taskq_thread+0x285
unix`thread_start+0x8
3221701
This happens in the sched (pid 0) process. My fsstat one looks like this:
# fsstat /conte...
2009 Aug 12
4
zpool import -f rpool hangs
I had the rpool with two sata disks in the miror. Solaris 10 5.10
Generic_141415-08 i86pc i386 i86pc
Unfortunately the first disk with grub loader has failed with unrecoverable
block write/read errors.
Now I have the problem to import rpool after the first disk has failed.
So I decided to do: "zpool import -f rpool" only with second disk, but it''s
hangs and the system is
2008 Feb 20
12
no luck with Xen....
Perhaps someone has ideas on this topic, a recent attempt to play with Xen was a reather unlucky event, all what I will be able to demonstrate on that system is a PV ONNV domU which
ikely will not be very attractive to the audience :(
HW: U40M2, 2 x 2 core AMD revF procs, 8GB MEM, Phonix BIOS 1.5 (latest)
1 x 200GB internal SATA drive
SW: dom0 ONNV build 82, latest VirtManager from
2006 Feb 24
17
Re: [nfs-discuss] bug 6344186
Joseph Little wrote:
> I''d love to "vote" to have this addressed, but apparently votes for
> bugs are no available to outsiders.
>
> What''s limiting Stanford EE''s move to using ZFS entirely for our
> snapshoting filesystems and multi-tier storage is the inability to
> access .zfs directories and snapshots in particular on NFSv3 clients.