search for: b35

Displaying 8 results from an estimated 8 matches for "b35".

Did you mean: 35
2006 Mar 20
1
ARC cache issues with b35/b36; Bugs 6397610 / 6398177
> Bug ID: 6398177 > Synopsis: zfs: poor nightly build performance in 32-bit mode (high disk activity) Part of the problem appear to be these kmem_caches: # mdb -k ... > ::kmastat cache buf buf buf memory alloc alloc name size in use total in use succeed fail ------------------------- ------ ------ ------ ---------
2010 Feb 04
1
Bug in as.character? (PR#14206)
...er formula is ok though. Best, H??vard ************ Browse[2]> formula.str y ~ -1 + b1 + b2 + b3 + b4 + b5 + b6 + b7 + b8 + b9 + b10 + b11 + b12 + b13 + b14 + b15 + b16 + b17 + b18 + b19 + b20 + b21 + b22 + b23 + b24 + b25 + b26 + b27 + b28 + b29 + b30 + b31 + b32 + b33 + b34 + b35 + b36 + b37 + b38 + b39 + b40 + b41 + b42 + b43 + b44 + b45 + b46 + b47 + b48 + b49 + elevation + f(idx, model = "sphere", sphere.dir = "global_temperature_80s", T.order = 2, K.order = 2, T.model = "rotsym", K.model = "rotsym", ini...
2006 Mar 03
5
flag day: ZFS on-disk format change
Summary: If you use ZFS, do not downgrade from build 35 or later to build 34 or earlier. This putback (into Solaris Nevada build 35) introduced a backwards- compatable change to the ZFS on-disk format. Old pools will be seamlessly accessed by the new code; you do not need to do anything special. However, do *not* downgrade from build 35 or later to build 34 or earlier. If you do so, some of
2006 Jun 06
1
[Fwd: Persistent "Abort due to systemic unresponsiveness"]
Just adding a few more details to the previous mail so that I can avoid some trouble for you folks. 1. I have done a /execname != "dtrace"/ to avoid dtrace itself causing more syscalls to be fired. 2. I have also supressed the printing on the terminal which makes dtrace slower. And what happens is this: dtrace -qn ''syscall::read:entry /execname != "dtrace"/ {
2015 Feb 17
10
[Bug 89186] New: Artifacts after waking up from suspend
...Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org Reporter: janluca at physik.fu-berlin.de QA Contact: xorg-team at lists.x.org Hi, I'm using a Lenovo Thinkpad T61 8889-B35 with a NVIDIA G86M [Quadro NVS 140M]. After waking the notebook up from suspend I get only black and white artifacts on my display. I can switch to the normal text-console tty without a problem. In the dmesg outputs there a follwing lines (full log attached): [ 625.471095] nouveau E[ PGRAPH][0...
2013 Apr 22
7
Multiple lon lat points in the map with ggplot2
Hello R users, For the last few days I am struggling with the following task: my data.frame: A1 A2 A3 B1 B2 B3 58.81 53.292 54.501 13.013 17.39 19.407 56.02 56.251 54.033 20.099 13.15 10.411 55.376 53.099 57.625 13.396 21.031 13.22 58.584 53.194 54.218 13.038 16.854 19.289 55.7 55.921 53.847 19.942 13.153 9.828 55.093 52.934
2006 Mar 23
17
Poor performance on NFS-exported ZFS volumes
I''m seeing some pretty pitiful performance using ZFS on a NFS server, with a ZFS volume exported (only with rw=host.foo.com,root=host.foo.com opts) and mounted on a Linux host running kernel 2.4.31. This linux kernel I''m working with is limited in that I can only do NFSv2 mounts... irregardless of that aspect, I''m sure something''s amiss. I mounted the zfs-based
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.