I lost my system volume in a power outage, but fortunately I had a dual boot and I could boot into an older opensolaris version and my raidz2 7 drive pool was still fine. I even scrubbed it, no errors. However, the older os has some smb problems so I wanted to upgrade to opensolaris11. I accidentally did the auto install option and it overwrote one of my data drives. This is really important data, but fortunately I have a raidz2, so how bad can it be?... BAD! Booting back into the earlier solaris version I cannot access my pool, This is what zpool status shows:
zpool status
pool: brick3
state: UNAVAIL
scrub: none requested
config:
I tried to export and re-import it, and I get the following message:
Hello,
We are using Solstice Disk Suite on Solaris 2.7.
We want to add two striped volume with six disks.
On each disk, we take a slice and we create the stripe.
That I want to know :
Is it necessary to add two replicas on the same slice on the new disks, as made before on the others... (1 Reply)
We have an application running on Win2K and this application ftp files to HP-UX using ftpdc as user id. The files are created in HP-UX with following permissions:
-rw-r----- 1 ftpdc users 968321 Apr 12 22:57 aaaa.txt
There is a job that runs on HP-UX trying to modify this file using the... (7 Replies)
First I would like to thank this forum for assisting me in setting up my 1st sunbox.
Could not have done it if it had not been for you guys and google :D
I have mirrored my box and have SUCCESSFULLY tested booting from the rootdisk and rootmirror successfully.
I am now looking at configuring... (2 Replies)
Good morning,
I have Solstice disk suite installed on my server.
One disk broke so I sostitute it.
A replica was present on this disk.
I had delete and then recreate it with commands metadb -d and metadb -a.
Now when I inquire for the status of replicas I see this:
stp11# metadb -i
... (2 Replies)
Hi,
when navigating on application webpages (peoplesoft applications) the users receive :
INSUFFICIENT AVAILABLE MEMORY.
I issued vmstat on UNIX server ( where is hosted Web server and application server and DB). Here is the result :
:vmstat 2 10
System configuration: lcpu=4 mem=30720MB... (8 Replies)
Hi,
When I execute one of my shellscript I am getting the below mentioned error message .This application takes 2input files which have the records counts 26463 and 1178046
exec(2): insufficient swap or memory available.
exec(2): insufficient swap or memory available.
exec(2): insufficient swap... (3 Replies)
Hi all,
I recently started exploring Solaris 10.
I am testing metadevices now.
I have been reading about the state databases here: 6.State Database (Overview) (Solaris Volume Manager Administration Guide) - Sun Microsystems
So I created 3 metadbs on 2 slices (6 in total; c1t1d0s3... (3 Replies)
Hey all!
I was hoping someone knew anything about this one...
I know with Solaris Volume Manager the default Database Replica size is 8192 blocks (4MB approximately)
Now I know you can increase this amount but is there any point?
The reason I am asking this is that I've setup mirroring on... (2 Replies)
Hi guys, I appreciate any help in this regard, we have lost sensitive data in the company.
One box with 2 disk mirrored and a 3ware controller handling 13 disks in a raidz2 pool. Suddenly the box restart and keeps "Reading ZFS config" for hours.
Unplugging disk by disk we isolate the disk... (3 Replies)
Discussion started by: tatxo
3 Replies
LEARN ABOUT DEBIAN
zfs-fuse
ZFS-FUSE(8) [FIXME: manual] ZFS-FUSE(8)NAME
zfs-fuse - ZFS filesystem daemon
SYNOPSIS
zfs-fuse [--pidfile filename] [--no-daemon] [--no-kstat-mount] [--disable-block-cache] [--disable-page-cache] [--fuse-attr-timeout SECONDS]
[--fuse-entry-timeout SECONDS] [--log-uberblocks] [--max-arc-size MB] [--fuse-mount-options OPT,OPT,OPT...]
[--min-uberblock-txg MIN] [--stack-size=size] [--enable-xattr] [--help]
DESCRIPTION
This manual page documents briefly the zfs-fuse command.
zfs-fuse is a daemon which provides support for the ZFS filesystem, via fuse. Ordinarily this daemon will be invoked from system boot
scripts.
OPTIONS
This program follows the usual GNU command line syntax, with long options starting with two dashes (`-'). A summary of options is included
below. For a complete description, see the Info files.
-h --help
Show summary of options.
-p filename --pidfile filename
Write the daemon's PID to filename after daemonizing. Ignored if --no-daemon is passed. filename should be a fully-qualified path.
-n --no-daemon
Stay in foreground, don't daemonize.
--no-kstat-mount
Do not mount kstats in /zfs-kstat
--disable-block-cache
Enable direct I/O for disk operations. Completely disables caching reads and writes in the kernel block cache. Breaks mmap() in ZFS
datasets too.
--disable-page-cache
Disable the page cache for files residing within ZFS filesystems. Not recommended as it slows down I/O operations considerably.
-a SECONDS --fuse-attr-timeout SECONDS
Sets timeout for caching FUSE attributes in kernel. Defaults to 0.0. Higher values give a 40% performance boost.
-e SECONDS --fuse-entry-timeout SECONDS
Sets timeout for caching FUSE entries in kernel. Defaults to 0.0. Higher values give a 10000% performance boost but cause file
permission checking security issues.
--log-uberblocks
Logs uberblocks of any mounted filesystem to syslog
-m MB --max-arc-size MB
Forces the maximum ARC size (in megabytes). Range: 16 to 16384.
-o OPT... --fuse-mount-options OPT,OPT,OPT...
Sets FUSE mount options for all filesystems. Format: comma-separated string of characters.
-u MIN --min-uberblock-txg MIN
Skips uberblocks with a TXG < MIN when mounting any fs
-v MB --vdev-cache-size MB
adjust the size of the vdev cache. Default : 10
--zfs-prefetch-disable
Disable the high level prefetch cache in zfs. This thing can eat up to 150 Mb of ram, maybe more
--stack-size=size
Limit the stack size of threads (in kb). default : no limit (8 Mb for linux)
-x --enable-xattr
Enable support for extended attributes. Not generally recommended because it currently has a significant performance penalty for many
small IOPS
-h --help
Show this usage summary.
REMARKS ON PRECEDENCE
Note that the parameters passed on the command line take precedence over those supplied through /etc/zfs/zfsrc.
BUGS /CAVEATS
The path to the configuration file (/etc/zfs/zfsrc) cannot at this time be configured.
Most existing packages suggest settings can be set at the top of their init script. These get frequently overridden by a (distribution
specific) /etc/default/zfs-fuse file, if it exists. Be sure to look at these places if you want your changes to options to take effect.
The /etc/zfs/zfsrc is going to be the recommended approach in the future. So, packagers, please refrain from passing commandline parameters
within the initscript (except for --pid-file).
SEE ALSO
zfs (8), zpool (8), zdb(8), zstreamdump(8), /etc/zfs/zfsrc
AUTHOR
This manual page was written by Bryan Donlan bdonlan@gmail.com for the Debian(TM) system (but may be used by others). Permission is granted
to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 any later version published by
the Free Software Foundation, or the Common Development and Distribution License.
Revised by Seth Heeren zfs-fuse@sehe.nl
On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL. The text of the
Common Development and Distribution Licence may be found at /usr/share/doc/zfs-fuse/copyright
COPYRIGHT
Copyright (C) 2010 Bryan Donlan
[FIXME: source] 2010-06-09 ZFS-FUSE(8)