andyleonard.com – zfs-snapshot.sh

Here’s a nice script found on thinking sysadmin. I slightly modified it to use the real mount point instead of assuming “/”, my changes are highlighted below:

#!/usr/local/bin/bash
# FROM: http://andyleonard.com/2010/04/07/automatic-zfs-snapshot-rotation-on-freebsd/

# Path to ZFS executable:
ZFS=/sbin/zfs

# Parse arguments:
TARGET=$1
SNAP=$2
COUNT=$3

# Function to display usage:
usage() {
scriptname=`/usr/bin/basename $0`
echo "$scriptname: Take and rotate snapshots on a ZFS file system"
echo
echo " Usage:"
echo " $scriptname target snap_name count"
echo
echo " target: ZFS file system to act on"
echo " snap_name: Base name for snapshots, to be followed by a '.' and"
echo " an integer indicating relative age of the snapshot"
echo " count: Number of snapshots in the snap_name.number format to"
echo " keep at one time. Newest snapshot ends in '.0'."
echo
exit
}

# Basic argument checks:
if [ -z $COUNT ] ; then
usage
fi

if [ ! -z $4 ] ; then
usage
fi

# Get the TARGET mountpoint
TARGET_MOUNT=$($ZFS get -H -o value mountpoint $TARGET)

# Snapshots are number starting at 0; $max_snap is the highest numbered
# snapshot that will be kept.
max_snap=$(($COUNT -1))

# Clean up oldest snapshot:
if [ -d ${TARGET_MOUNT}/.zfs/snapshot/${SNAP}.${max_snap} ] ; then
$ZFS destroy -r ${TARGET}@${SNAP}.${max_snap}
fi

# Rename existing snapshots:
dest=$max_snap
while [ $dest -gt 0 ] ; do
src=$(($dest - 1))
if [ -d ${TARGET_MOUNT}/.zfs/snapshot/${SNAP}.${src} ] ; then
$ZFS rename -r ${TARGET}@${SNAP}.${src} ${TARGET}@${SNAP}.${dest}
fi
dest=$(($dest - 1))
done

# Create new snapshot:
$ZFS snapshot -r ${TARGET}@${SNAP}.0

Thanks Andy!

FreeNAS CIFS/Samba changing Guest Account ‘FTP’ not working

Using FreeNAS 0.7 Khasadar (revision 4919) with CIFS/SMB Authentication Anonymous, I changed the Guest account for but it is not actually applying it to the configuration, it is a trivial bug and here’s a small dirty workaround.

1 – Create an excutable file containing this:

[bash]
#!/bin/sh

# find and replace ‘ftp’ by ‘transmission’
sed -i. ‘s/ftp/transmission/g’ /etc/rc.d/samba

# restart samba to use the new config
/etc/rc.d/samba restart
[/bash]

2 – Go in System|Advanced|Command scripts and add an entry for your script in “PostInit”

For those who are interested, I am doing this because my network is not accessible from the outside and I didn’t want to bother with user privileges. I am using my FreeNAS box to share media files downloaded using Transmission and I wanted everybody to be able to access/modify/delete them, so I change the guest account to be “transmission” 🙂

FreeNAS (embedded) iconv command

To install iconv on a “data” parition:

export PKG_TMPDIR=/mnt/usb-data/temp
pkg_add -r iconv -P /mnt/usb-data/pkg

And execute this at boot time:

ln -s /mnt/usb-data/pkg/bin/iconv /bin/iconv

Useful tools in an “embedded” FreeNAS: wget and bash

wget

To install wget on a “data” parition:

export PKG_TMPDIR=/mnt/usb-data/temp
pkg_add -r wget -P /mnt/usb-data/pkg

Now we need a script to create the symlinks to the wget binaries in the “pkg” directory:

nano /mnt/usb-data/hooks.sh

Here’s the content:

#!/bin/sh

ln -s /mnt/usb-data/pkg/bin/wget /bin/wget

Now make it run at boot time, go in System —> Advanced —> Command scripts and enter:

/mnt/usb-data/hooks.sh

Select PostInit and that’s it! Everytime you reboot your FreeNAS server the symlinks will be re-created!

bash

For bash, add this in the “hooks.sh” script:

# .bashrc for root
ln -s /mnt/usb-data/bashrc /root/.bashrc

# .bashrc for regular user
ln -s /mnt/usb-data/bashrc /mnt/.bashrc

# automatically load bash for root on login (not clean but works)
echo "bash --init-file /mnt/usb-data/bashrc" >> /root/.cshrc

# automatically load bash for regular user on login (not clean but works)
echo "bash --init-file /mnt/usb-data/bashrc" >> /mnt/.cshrc

Vim (Vi IMproved) in an “embedded” FreeNAS

You need an embedded install with a data partition. My FreeNAS server runs from a 1GB usb stick and the data partition is mounted as “/mnt/usb-data”. To install Vim on the usb stick:

# using csh
setenv PKG_TMPDIR /mnt/usb-data/temp

# install package
pkg_add -r vim-lite -P /mnt/usb-data/pkg

Now we need a script to create the symlinks to the Vim binaries in the “pkg” directory:

nano /mnt/usb-data/hooks.sh

Here’s the content:

[bash]#!/bin/sh

# Vim symlinks to binaries
ln -s /mnt/usb-data/pkg/bin/vim /bin/vi
ln -s /mnt/usb-data/pkg/bin/vim /bin/vim

# .vimrc for root
ln -s /mnt/usb-data/pkg/share/vim/vim72/vimrc_example.vim /root/.vimrc
# .vimrc for regular user
ln -s /mnt/usb-data/pkg/share/vim/vim72/vimrc_example.vim /mnt/.vimrc

# syntax file
mkdir /usr/local/share/vim/
mkdir /usr/local/share/vim/syntax/
ln -s /mnt/usb-data/pkg/share/vim/vim72/syntax/syntax.vim /usr/local/share/vim/syntax/syntax.vim[/bash]

Now make it run at boot time, go in System —> Advanced —> Command scripts and enter:

/mnt/usb-data/hooks.sh

Select PostInit and that’s it! Everytime you reboot your FreeNAS server the symlinks will be re-created!

My FreeNAS/FreeBSD configuration on D945GCLF2 / Atom 330 VS “panic spin lock held too long”

UPDATE 2010-05-20
I am now running 0.7.1 Shere (revision 5127) since 1 month with Hyperthreading enabled and I had no issue. It seems to be fixed.

UPDATE 2009-09-03
Still running without any issues 🙂

UPDATE 2009-08-01

Re-installed FreeNAS this weekend and the problem didn’t come back!
Disabling Hyperthreading fixed it!

UPDATE 2009-07-26

Disabling Hyperthreading in the Bios seems to do the trick, I haven’t yet got the error again, I am crossing my fingers.

UPDATE 2009-07-21

Now I am trying to disable Hyperthreading to see if my problem will go away, stay tuned.

ORIGINAL POST

I had some “panic spin lock held too long” problem, my FreeNAS box was freezing without any reasons.

Here’s what I did:

  1. Resetted the Bios to default settings (I had turned OFF many things before)
  2. Installed using full install amd64 (I was using an embedded install before)
  3. System -> Advanced -> activated Power Daemon
  4. Network -> LAN -> activated Device Polling
  5. Network -> LAN -> Type 1000baseTX / Full-Duplex

And since then no more “panic spin lock held too long”.

Unfortunately, the problem came back 🙁 It seems to be related to when I leave mounted shares on my Ubuntu dektop for a long period without activity. I re-installed my NAS directly with FreeBSD/Samba and the same problem happened again.

Interesting feed: http://lists.freebsd.org/pipermail/freebsd-stable/2009-July/thread.html#51019