Tag Info

New answers tagged

1

Just a very wild shot in the dark; netatalk documentation tells this: The AFP protocol mostly refers to files and directories by ID and not by name. Netatalk needs a way to store these ID's in a persistent way, to achieve this several different CNID backends are available. The CNID Databases are by default located in the ...


0

So what does a traceroute from a 192.168.200.0/24 machine to the other 192.168/16 look like: does the trail end at the router, or is something else eating the packets? If it does end at the router, try turning up the verbosity of your ipfw (with pf you would add a log option to the drop/deny rules).


0

... that behaviour start to happening after implementing this: return error 410 for location regex? in nginx - Server Fault after retweaking it, it's now working as expected: # cat X.conf server { listen X.X.X.X:80; server_name X; root /home/X/X/; index index.php; location ~ \.php$ { include ...


1

As told above, try first: # setenforce 0 if the files appear, then it's a SELinux missing context. Enable SELinux again, then add context to folder: # setenforce 1 # chcon -Rt samba_share_t /usr/share/nginx/www/


0

FreeBSD crashes because of this error: an 21 22:19:44 s-FreeNAS kernel: (ada0:ahcich0:0:0:0): READ_FPDMA_QUEUED. ACB: 60 08 70 02 00 40 00 00 00 00 00 00 Jan 21 22:19:44 s-FreeNAS kernel: (ada0:ahcich0:0:0:0): CAM status: ATA Status Error Jan 21 22:19:44 s-FreeNAS kernel: (ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC ) Jan ...


2

Even though the question is more than half a year old, since I just had the same problem Don't configure your IP address on the physical member interfaces of the bridge but the bridge interface itself. This is mentioned in the FreeBSD handbooks section on bridging. My understanding is that this is due to the way the packets are processed. if_bridge(4) ...


0

The PF firewall has NAT and redirection build right in. Add this to /etc/rc.conf: gateway_enable="YES" pf_enable="YES" And configure the firewall. Add these lines to /etc/pf.conf: ext_if=em0 ext_addr = N.N.N.N (your external IP) int_if=em1 int_net=10.0.0.0/8 int_addr=10.0.0.1 libcap_host=10.0.0.2 nat on $ext_if from $int_net to any -> $ext_addr rdr ...


0

Reported errors do not necessarily mean the drive is failing. A sector may have just gone bad and been replaced from the reserve pool. ZFS will automatically repair any corrupted data with good data from the other drives. If the number of errors keeps increasing however that means more sectors are going bad and is a sure sign of a drive about to fail. ...


1

FreeBSD limits the length of mount point names to 88 chars. The reasons for this are somewhat esoteric, but has to do with aligning a memory structure on page boundaries[1]. You can patch the mount binary to use a larger limit or to remove it all together[2] but this may cause crashes. I have successfully removed the check (also for vagrant with nfs) and ...


1

#1) Chrooting virtual hosts individually is not supported. The "Context" for the ChrootDir directive is "server config," and thus... "This means that the directive may be used in the server configuration files (e.g., httpd.conf), but not within any <VirtualHost> or <Directory> containers. It is not allowed in .htaccess files at all." [1] It is ...


0

The Ports Collection is a set of Makefiles, patches, and description files stored in /usr/ports. This set of files is used to compile and install applications on FreeBSD. From FreeBSD Handbook: 5.5. Using the Ports Collection Ports are one of the most powerful features of FreeBSD. You can search and browse the ports collection easily at FreshPorts.


1

Using ZFS + VMware + NFS is a terrible idea. It will get you the worst result. Vmware uses an implementation of NFS that need constantly to do SYNCed writes, and wait for each one to do so. And this is extremely slow on ZFS.. ZFS first writes in the ZIL log and a lot latter do the actual wirte on disks (and only then confirm the sync write). I got 5MB/s on ...


0

You can use the "-alldirs" parameter: /storage -alldirs -maproot=nobody client


1

The TERM environment variable probably won't be enough, because we are talking not about the cursor moving maneuvers, but about the command line editing tool. You need to set up in your command line editing library, which command can enable the cursor moving in the different directions. Your shell is probably bash, which uses the readline library for ...


2

I have figured this out thanks to @citrin's comment. Adam Weinberger reported this as a bug here. He also provided two patches for two different desirable options: pre-building the man pages, or building cmake without them. I opted for the latter one. The attachment here includes little fixes to the Makefile and pkg-plist of the corresponding port. I just ...


1

Have a look in /etc/termcap or /etc/terminfo (not sure which one FreeBSD uses) if there is a termcap entry for xterm-256color. If yes, it is probably wrong (or whatever program you are in is not correctly using the terminal information but trying to parse terminal codes manually; if you have a version of GNU Bash on your FreeBSD, try starting this one and ...


-1

To disable history for tcsh/csh type the following: unset history; unset savehist or you can also do the following: set history = 0; set savehist = 0 Either one will disable history from being saved. You can also edit the ~.cshrc file and change the following: set history = 1000 set histsave = 1000 to set history = 0 set histsave = 0 Then ...


0

Chances are that you have HW RAID enabled in mode 0 or 1 and the controller is presenting one unified disk to FreeBSD. You either have to configure your controller for JBOD or if that's not supported then set up a RAID 0 array for each disk in your system.


1

If you can't use single user due to ACPI, use the interactive boot loader option to disable ACPI, then add hint.acpi.0.disabled=1 to /boot/loader.conf as the previous answer suggested.


1

Impossible to say what happened during your install without more info which at this point is probably not available. In theory, even if your HW RAID was enabled and therefore the OS only saw 1 physical disk, you should still be able to put ZFS on that, though it would be a bad idea. It's always better to disable the hardware RAID when using ZFS. You should ...


1

1) This is not the handbook, this is a man page for acpi. 2) You could disable the entire ACPI, add hint.acpi.0.disabled=1 to the /boot/loader.conf and reboot.


2

No. Don't do it. Any form of backup that revolves around intentionally failing an array or pool of disks is fraught and irresponsible. If you could provide details about your rsync command line, what you're transferring, the connection between the servers and any other specifics, we may be able to help with a more robust solution.


1

Create an rc script, e.g. #!/bin/sh # PROVIDE: gnop disks # BEFORE: fsck . /etc/rc.subr name="gnop" start_cmd="${name}_start" stop_cmd= gnop_start() { local disk="/dev/da1" /sbin/gnop create -S 4096 "$disk" || err 1 "Creating gnop on $disk failed" } load_rc_config $name run_rc_command "$1" where /dev/ada1 This could be extended to created ...


3

Please run: zpool scrub tank And then look a little more into the properties and attitudes of ZFS and how it tries to protect data.



Top 50 recent answers are included