Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages


home | help
ChironFS(8)		      Kernel/Filesystems		   ChironFS(8)

       ChironFS	- The Chiron Replication Filesystem version 1.1

       chironfs	[-?fhlqV] [--fuseoptions <fuse options>] [--help]
		[--version] [--log <logfilename>]
		[--quiet] [--ctl <controlfilesystempathname>]
		[:]path=[:]path[=[:]path[=[:]path...]] mount-point

	   By providing	a mountpoint with this option, ChironFS
	   will	also mount a proc-like filesystem intended to
	   enable administrative functions of the replication
	   filesystem. Currently you can check the status of
	   each	replica	and manually change it.	So, you	can
	   force disable a replica and,	if you have already
	   reoperated a	replica	and synchronized it with the
	   others, you may tell	ChironFS to use	it again.
	   The control filesystem is composed of one directory
	   for each replica, containing	two files: the first is
	   named "status" and contains a number	"0" for	replicas
	   in good state or a number "2" if the	replica	is
	   disabled and	the data is inconsistent. By echoing
	   "0" or "2" in this file you enable or disable the
	   replica. The	second file, named "",
	   is a	script intended	to run as a nagios plugin. If
	   you want to use it, do not copy it to another path,
	   because its contents	change dynamically and it will
	   not work in another path. You cannot	change ownership
	   or permission bits on any of	the files/directories
	   in this filesystem. To configure who	can access it,
	   change the ownership	of its mount point BEFORE
	   mounting it.	ChironFS will use this ownership to all
	   files and directories under it.

	 --fuseoptions FUSE OPTIONS, -f	FUSE OPTIONS
	   Here	you can	set Fuse specific options:
		-d -o debug
		   enable debug	output (implies	-f)
		   foreground operation
		   disable multi-threaded operation
		-o allow_other
		   allow access	to other users
		-o allow_root
		   allow access	to root
		-o nonempty
		   allow mounts	over non-empty file/dir
		-o default_permissions
		   enable permission checking by kernel
		-o fsname=NAME
		   set filesystem name
		-o max_read=N
		   set maximum size of read requests
		-o hard_remove
		   immediate removal (don't hide files)
		-o use_ino
		   let filesystem set inode numbers
		-o readdir_ino
		   try to fill in d_ino	in readdir
		-o umask=M
		   set file permissions	(octal)
		-o umask=M
		   set file permissions	(octal)
		-o uid=N
		   set file owner
		-o gid=N
		   set file group
		-o entry_timeout=T
		   cache timeout for names (1.0s)
		-o negative_timeout=T
		   cache timeout for deleted names (0.0s)
		-o attr_timeout=T
		   cache timeout for attributes	(1.0s)
	   See Fuse specific documentation for more help.
	 --help, -h, -?
	   Prints the help
	 --log FILE, -l	FILE
	   Sets	a log filename.	If you don't set it, no	log will be
	   done	at all
	 --fsname NAME,	-n NAME
	   Defines the filesystem label	name, for viewing it in	df
	   or mount
	 --quiet, -q
	   Do not print	error messages to stderr, just set the exit
	   codes. This does not	affect logging
	 --version, -V
	   Prints version of the software

	   This	the "="	separated list of paths	where the
	   replicas will be stored. If a replica path is prefixed
	   with	a colon, then that replica will	be considered
	   slower than the others and the load balance algorithm
	   will	choose it for read only	if the faster replicas

	   The mount-point through which the replicas will be

       This man	page is	correct	for version 1.1	of the Chiron File System.

       If you specify a	log file using the -l or the --log command line	option
       you will	have critical failures reported	in that	file.  There  are  two
       types  of  reports in this file:	the failure report and the disable re-
       port. The failure report	indicates the action failed, the path  of  the
       replica	that  failed and the related errno message. The	disable	report
       just tell us that a replica is being disabled and so it's inconsistent.
       The  reintegration  process  of the replica have	to be made manually in
       this version. We	suggest	you use	rsync to do it.	After  the  data  syn-
       chronization  you  have	to remount the chiron filesystem. A replica is
       disabled	ONLY IF	a write	operation was FAILED in	the  disabled  replica
       AND the same operation was SUCCESFULL in	another	replica.

       rsync(1),  heartbeat at .

       The  ChironFS replication Filesystem  were  created  by	Luis Otavio de
       Colla Furquim.

Luis Otavio de Colla Furquim	      1.1			   ChironFS(8)


Want to link to this manual page? Use this URL:

home | help