Hot answers tagged

12

If you store the snapshots in files, as opposed to in the file system (e.g. with zfs receive), I'm afraid, this is not possible. ZFS on the receiving side If you use ZFS on the sending and on the receiving side you can avoid having to transfer the whole snapshot and only transfer the differences of the snapshot compared to the previous one: ssh myserver '...


10

You aren't really supposed to use the shell on the main FreeNAS host, and so the pkg repositories are disabled. If you want a shell on the machine you should look at creating a Jail (like a lightweight virtual machine) and use that for shell access. If you really want to use pkgon the main FreeNAS host and you're confident that you can clean up any mess ...


7

The solution mentioned here is good, but I was looking for one which didn't require ~/.ssh to be present or required an attempt for it to be created (running on Windows, distributing a MSYS built ssh.exe, but running on other machines without MSYS/Cygwin installed). Unfortunately, it appears the routine is hardcoded in the source code, regardless of what ...


5

You can use diff to compare two file hierarchies: diff -qr /path0 /path1 Flag -r asks to walk directories recursively, while -q asks to just print a statement when files differ, not the detailed differences. This command prints nothing and exits with status 0 when the the directories are identical. If you would like a message for each comparison, not just ...


5

You need to install/update your ports catalogue first. Run these commands first: portsnap fetch update portsnap extract you can then run your: pkg install mysql55-server (note: it is mysql55-server and not mysql-server)


5

Remount the root filesystem read-write temporarily and make a symbolic link for .ssh that points somewhere where ssh can write. This way you can also do things like add ssh keys in the future, or allow new known_hosts without having to go to extra strenuous steps. And you could get rid of your -o UserKnownHostsFile option at the same time.


4

A NAS is a storage device connected to a network. Its purpose is to serve files to clients using some file sharing protocol like NFS, SMB/CIFS, AFS and the likes. A SAN is a network interconnecting storage (arrays) to clients. Its purpose is to provide block level access to disk devices (LUNs). iSCSI is clearly a low level protocol so belongs to the SAN ...


4

On the source drive use find, xargs and md5sum: find . -type f | xargs md5sum > sums.md5 copy that file to the destination machine (if different) and there do: md5sum -c sums.md5 The advantage of this is that if you could run the check on the server, which is normally much faster than reading (or comparing), over the network. Not having to have the ...


4

Disclaimer: I do not have many links and references to back up all below at hand at the moment, and I did not test it extensively. This is just a summary of things I have read over the last five to seven years about ZFS and how it works, and some limited own testing (not coordinated, but mostly random reboots). Also, everything below is said without ...


3

camcontrol it the proper tool for the purpose when using both ATA and SCSI disks. You even state you tried it - but not why you could not use it. A typical output would be: # camcontrol devlist at scbus1 target 0 lun 0 (ada0,pass0) at scbus2 target 0 lun 0 (ada1,pass1) at scbus4 target 0 lun 0 (ada2,pass2) at scbus5 target 0 lun 0 (ada3,pass3) ...


3

For NTFS In researching this I found this AskUbuntu Q&A titled: How do I use 'chmod' on an NTFS (or FAT32) partition?. According to this thread there are several ways to go about this. Methods Control the permissions at mount time. $ sudo mount -t ntfs -o \ rw,auto,user,fmask=0022,dmask=0000 /dev/whatever /mnt/whatever Using a user mapping file ...


3

Answering my own question after some more searching: I understand that this can't be done like this because mount_smbfs is FreeBSD-specific and it hasn't kept pace with samba features available in Linux (whereas smbclient has). This isn't quite the end though. You can run a virtual Linux machine in a jail on FreeNas and then connect to the Time Capsule ...


3

It's in the su(1) man page. PAM is used to set the policy su(1) will use. In particular, by default only users in the "wheel" group can switch to UID 0 ("root"). This group requirement may be changed by modifying the "pam_group" section of /etc/pam.d/su. See pam_group(8) for details on how to modify this set- ting. A very ancient version of the man ...


2

There is a FreeNAS7 repository in the FreeNAS github repository which has some of the documentation that you're looking for. Specifically there's a docs directory which has some of the documentation.


2

I always add -v switches to rsync when attempting to debug what's going on. $ rsync -v .... If you need more verbosity add more -v switches: $ rsync -vv Since you've already added -v and it's not giving you any additional insights it's unlikely that more -v's will do much else. Debugging further Idea #1 Since you're issue seems to be specific to this ...


2

There are several ways to create a SoftRAID with Linux: LVM's internal RAID and four versions of MD RAID (mdadm): 0.90, 1.0, 1.1, 1.2. Every non-ancient Linux should understand them all. There should not be any problem with a distro change.


2

A Network Attached Storage (NAS) device is normally used as a storage device that shares data over the network. What you are trying to achieve is possible in theory, but it is very uncommon and may therefore be hard to get working. First of all, support for Thunderbolt is quite low in open source operating systems. As you figured out, FreeBSD has no support ...


2

From the 9.30 GUI, go to Plugins, then click the installed tab (the default tab is All), then select and hit delete on the jail that you need to remove.


2

ACLs, if present, override the usual chmod bits. Also, NFSv4 ACLs don't have masks. I believe the problem here is you only set 'rwx', and not 'rwxp'. The 'p' is APPEND_DATA/ADD_SUBDIRECTORY, which is what controls... well, adding subdirectories.


2

You were unable to just? $ exit


2

The errors regarding hostname lookups means you do not have DNS configured for your LAN. To get rid of these messages you have to uncheck Hostname lookups on the CIFS settings.


2

Due to a delay in getting a response from this forum, I decided to post the question to the FreeNAS forums. Dru Lavignue from iXSystems reponded with the following answer: If you set a property on a dataset, only that dataset (and its child datasets that aren't explicitly set differently) is affected by the ramifications of that property.


2

“AMD Chipset Driver” refers to the drivers for Windows; this isn’t a concern on FreeNAS.


2

It appears that the root cause is connected to the fact that Brian has to: This is also the only share I have where random new folders fail to inherit the permissions from the share folder correctly, maybe 1-2 times a day I have to manually set a folders permissions correctly (folders created by a service I have running on this machine) The samba fails ...


2

What you see on bugs is conversation regarding updating to unifi6. It's not available in ports right now but, since the PR was only filed six days ago, it looks like someone is very, very close to completing it. In the meantime, it's not available anywhere from FreeBSD itself. The best you could do right now is try to install it yourself from the unifi site ...


1

You must be reading some very old doc, pkg_add has been gone from FreeBSD for quite a while. Instead, use pkg. And, we have good binary packages now, so there's no need install portmaster and then compile from source. Instead, just install vim directly by doing pkg install vim or if you prefer not to have the X11 version, pkg install vim-lite.


1

Just found one way... A grep at dmesg.boot where scbus# is the SCSI ID and target # the address at this ID. jdivm13# grep "da[0-9] at" /var/run/dmesg.boot da0 at mpt0 bus 0 scbus2 target 0 lun 0 da1 at mpt1 bus 0 scbus3 target 1 lun 0 da2 at mpt1 bus 0 scbus3 target 2 lun 0 da3 at mpt1 bus 0 scbus3 target 3 lun 0 da4 at mpt1 bus 0 scbus3 target 4 lun 0 da5 ...


1

This was happening to me. I deleted a .tmux file in my home directory, and that fixed it. You could also try tmux kill-server.


1

If you use ACLs, the classic group permissions turn into the so called mask, which determines the maximum permissions you can effectively give per setfacl, eg. ls -k shows -rw-r--r--+ root root and you have setfacl -m g:users:rw because the mask is only read getfacl will show you: group:users:rw effective r So set group to rw or rwx by classic chmod ...


1

I had a similar issue on FreeNAS 9.3 and could not find a remove button. I got it to disappear by going to the jails volume, and removing the directory which held the jail: # rm -fr /mnt/black/jails/.couchpotato_1.meta/ This also removed the complaints during boot. No negative side effects seen yet.


Only top voted, non community-wiki answers of a minimum length are eligible