06-03-2010
No nothing has been changed on the server .. The host is up and running since 250 days and we are not using rcapd for memory capping though we have enabled max-shm and max-locked memory for other zones but not for this ( problematic) zone. We did remove the resource capping on this zone
8 More Discussions You Might Find Interesting
1. Solaris
I 've a weired situation .. my system has zfs root as its file system and now root file system is full at 100%
# zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 134G 65.2M 94K /rpool
rpool/ROOT ... (1 Reply)
Discussion started by: fugitive
1 Replies
2. Solaris
I have created a flash archive from a Ldom on T5220 with zfs root solaris 10_u8. But after creation of flar the info shows the
content_architectures=sun4c,sun4d,sun4m,sun4u,sun4us,sun4s
but not sun4v due to which i 'm unable to install this flash archive on another Ldom on the same host. Is... (0 Replies)
Discussion started by: fugitive
0 Replies
3. Solaris
Hi All,
I am trying to read zpool.cache file to find out pool information like pool name, devices it uses and all properties.
File seems to be in packed format.I am not sure how to unpack it.
But from opensolaris code base we can see that they have used libz for uncompromising this file, but... (0 Replies)
Discussion started by: shailesh_111
0 Replies
4. Solaris
Greetings Forumers!
I have a Solaris 10u9 M5000 with 32GB RAM and have noticed the ZFS arc cache is consuming large amount of memory. Here's what I see on my system:
# echo ::memstat|mdb -k
Page Summary Pages MB %Tot
------------ ---------------- ... (9 Replies)
Discussion started by: bluescreen
9 Replies
5. Solaris
I 'm tryin to install a solaris server After all the system initialization & extraction of flash archive installation aborts with following error ..
Does anyone know what could be the issue for the same ?
Any help would be appreciated
Extracted 2205.05 MB ( 99% of 2205.54 MB... (6 Replies)
Discussion started by: fugitive
6 Replies
6. Solaris
I jumpstarted a solaris sun4u box from WANboot and it completed but while coming up it gives following error and panics
Use is subject to license terms.
NOTICE: zfs_parse_bootfs: error 48
Cannot mount root on rpool/47 fstype zfs
panic/thread=180e000: vfs_mountroot: cannot mount root
... (0 Replies)
Discussion started by: fugitive
0 Replies
7. Solaris
Hi,
kstat -p -m zfs -n arcstats -s size returns
zfs:0:arcstats:size 8177310584
this values is approx (7.61 GB)
but my Physical Memory size is only 6144 Megabytes.
Can this happen ?
if yes, then how can I find free memory on the system.
BTW, I ran the kstat commands from a Non... (2 Replies)
Discussion started by: sapre_amit
2 Replies
8. UNIX for Beginners Questions & Answers
Hi All,
How do we calculate the zfs cache value from Solaris 11.3 ?? I normally use memstat but learnt that is not a good practice. Any other way to get the value ? (2 Replies)
Discussion started by: jayadanabalan
2 Replies
LEARN ABOUT OSF1
named-xfer
named-xfer(8) System Manager's Manual named-xfer(8)
NAME
named-xfer - Pulls BIND zones from another server
SYNOPSIS
/usr/sbin/named-xfer -z zone_to_transfer -f db_file -s serial_no [-d debug_level] [-l debug_log_file] [-t trace_file] [-p port] [-S]
servers...
OPTIONS
Specifies the name of the BIND zone for the named-xfer daemon to transfer, for example, dec.com. This option is required to pull a zone.
Specifies the name of the file into which the pulled zone information is placed. This option is required to pull a zone. Specifies the
current serial number of the SOA record for the zone zone_to_transfer. If serial_no is set to 0, the zone is always pulled. This option is
required to pull a zone. Sets the debug level and determines the amount of debug information to be displayed. Specifies the file that
will contain any debug messages from the zone pull. Specifies the file that will contain a trace from the zone pull. Specifies the port
that will be used instead of the default name server port listed in /etc/services. Performs a restricted transfer of only the SOA, NS
records and glue A records for the zone. The SOA record is not loaded by named, but is used to determine when to verify the NS records.
See named(8) for more information. Specifies a list of Internet addresses, in dotted-quad format, from which to pull a zone. If the first
host cannot be reached, the named transfer daemon tries to pull the zone from the next host listed.
DESCRIPTION
The named transfer daemon, /usr/sbin/named-xfer, is a server that is usually run by the named daemon, /usr/sbin/named, but it can also be
run manually with the given arguments. The named transfer daemon runs on a BIND secondary server and pulls BIND zones from a primary
server. This daemon is not run by default, nor can it be started up from inetd(8).
SEE ALSO
Commands: named(8)
Files: resolver(4), services(4)
named-xfer(8)