Tagged: NAS RSS

  • Jonny Gerold 2:48 am on November 22, 2009 Permalink | Reply
    Tags: beadm, dedup, NAS, pkg repos   

    ZFS Dedup | OpenSolaris repos | beadm 

    DEDUP IS AMAZING. Can’t wait to try it out, but I’m waiting for my system to upgrade from the dev repository, err, I might just hold off cause it’s taking forever. Maybe I’ll play with it in a VM, instead of my Home NAS :*
    Anywho please read up on it here: http://blogs.sun.com/bonwick/entry/zfs_dedup

    It’s an amazing technology, and I’m super happy that it’s finally out.

    ——

    Just in case you want to upgrade 111b to 127, or just have the most up to date packages try the following:

    pkg set-publisher -O http://pkg.opensolaris.org/dev "opensolaris.dev"
    pkg set-publisher -P opensolaris.dev
    

    Now when you look at your repos, dev is default or ‘preferred’

    fsk141@TrayNAS:/mnt$ pkg publisher
    PUBLISHER                             TYPE     STATUS   URI
    opensolaris.dev          (preferred)  origin   online   http://pkg.opensolaris.org/dev/
    opensolaris.org                       origin   online   http://pkg.opensolaris.org/release/
    

    ——

    As I work with OpenSolaris I am continually amazed, and pissed off at the same time. Where some things are insanely simple and straightforward. Other things are tedious, and hard because of my Linux background. Another thing that I am letdown is the lack of community like Arch Linux. There is a very large OpenSolaris community, but not in the sense of packages, and a lot is left to you (as in manually compile)
    ——

    One of the difficult concepts to grasp is the boot environment concept. It’s kinda like a snapshot of sorts for your boot environment. Since OpenSolaris isn’t a rolling distro like Arch Linux, there are different revisions. Well instead of forcing some difficult reinstall you can simply ‘pkg image-update’ and upon your next reboot you have your new environment. You also have the ability to easily revert.

    fsk141@TrayNAS:/mnt$ beadm list
    BE             Active Mountpoint Space   Policy Created
    --             ------ ---------- -----   ------ -------
    TrayNAS_Nov_21 -      -          304.15M static 2009-11-21 15:53
    opensolaris    -      -          7.57M   static 2009-10-16 08:19
    opensolaris-1  NR     /          3.62G   static 2009-11-22 01:44
    
    fsk141@TrayNAS:/mnt$ beadm destroy TrayNAS_Nov_21
    Are you sure you want to destroy TrayNAS_Nov_21? This action cannot be undone(y/[n]): y
    

    beadm is a great tool to modify your BE, and I love the simplicity in the BE scheme.

     
  • Jonny Gerold 12:00 pm on November 21, 2009 Permalink | Reply
    Tags: NAS,   

    Opensolaris blast on the way. 

    I was planning to put one giant post on how to setup a NAS with Open Solaris & NAS. Yet I think it would be nice to have a few key posts, and then group them together in the end. I just installed Open Solaris on my new machine. And am starting the setup… More to come soon.

     
  • Jonny Gerold 3:14 am on October 6, 2009 Permalink | Reply
    Tags: images, , NAS, picasa,   

    Image Organization | In-N-Out NAS 

    It’s painful, but I’ve been meaning to get my images in good order for a long time now. Well I made a little script to rename all the JPG & AVI extensions to lower case, and remove the IMG_0 crap.

    #!/bin/bash
    
    mmv "*.JPG" "#1.jpg"
    mmv "IMG_0*" "#1"
    
    mmv "*.AVI" "#1.avi"
    mmv "MVI_0*" "#1"
    
    chmod 755 *
    

    mmv is a powerful tool, and I’m using a very simple implementation of it. I’ve gotten all my images in order at the moment, and right now I’m pushing everything into Picasa 3.5 to get all the faces recognized. This is an excellent selling point of Picasa 3.5. It works pretty well, and my overall experience with Picasa has been excellent. Well I’m off to sleep for now, but an update is soon to come with my overall experience of Picasa.

    ——
    The In-N-Out NAS is at a major standstill at the moment. I didn’t think a 32 bit system would be a problem when I purchased the VIA board. Yet I forgot about the “performance benefit” with ZFS & 64 bit. Well come to find out, 32 bit is restricted to 1TB or less. Anything higher is rejected with a nice little ‘f you for using 32 bit’ message in ‘/var/adm/messages’ In the mean time I’m trying to get a new motherboard, prolly core duo mini-itx intel board. The overall experience of this homebrew NAS has been an unsavory experience, yet it looks great, and once everything is worked out, I should have a wonderful NAS setup.

     
  • Jonny Gerold 12:00 am on December 10, 2008 Permalink | Reply
    Tags: , NAS, ,   

    How to create zfs stripe (pool) [NAS] 

    I recently (Last night to be exact) I installed Open Solaris as my NAS/Backup Server. Why you may ask? Well I love Arch Linux yet see the *need* to start using ZFS. ZFS is freakin-fan-tastic. It’s puts the S in simple, and allows you to have a filesystem that does much more than a common file system. Such as NFS, SMB, and Compression (did I mention that this is all built in :) I’m going to go through the simple process to setup a zfs striped pool, and setup a few datasets, and apple compression.

    OpenSolaris tools I’ll cover:
    format
    zfs(1M)
    zpool(1M)

    Lets start out by finding the disks that we would like to add to the pool:

    root@Nom:~# format < /dev/null
    

    Which will look like this:

    root@Nom:~# format < /dev/null
    Searching for disks...done
    
    AVAILABLE DISK SELECTIONS:
           0. c3d0 
              /pci@0,0/pci-ide@1f,1/ide@0/cmdk@0,0
           1. c4d1 
              /pci@0,0/pci-ide@1f,2/ide@0/cmdk@1,0
           2. c5d0 
              /pci@0,0/pci-ide@1f,2/ide@1/cmdk@0,0
    Specify disk (enter its number):
    

    This shows the three disks that are present in my system. I'll break it down a little. The number you see at the beginning is the number as per the format command. Then the information in the <>'s displays a disk ID, size of the disk, and some other little tidbits for the people that care.

    What you're looking for is "c4d1" & "c5d0" which are the two Western Digital 1TB disks that I'm going to make my pool with.

    To create the pool use the zpool command:

    root@Nom:~# zpool create nom c4d1 c5d0
    

    That's it, you've now created your first zfs pool. Just to sum up what I just did, I formatted the disks, set the mountpoints, mounted the device, and now have an active zfs pool.

    If you would like to see the zpools that you currently have do the following command:

    root@Nom:/nom# zpool list
    NAME    SIZE   USED  AVAIL    CAP  HEALTH  ALTROOT
    nom    1.81T  82.5K  1.81T     0%  ONLINE  -
    rpool   149G  3.36G   146G     2%  ONLINE  -
    

    I could go ahead and add a NFS share and Compression yet, why not stay organized :) I would rather create individual file systems to store the different data that I have.

    To show what I mean I'll show you what a zfs file system is:

    root@Nom:/nom# zfs list
    NAME                       USED  AVAIL  REFER  MOUNTPOINT
    nom                       70.5K  1.78T    18K  /nom
    rpool                     4.36G   142G    72K  /rpool
    rpool/ROOT                2.37G   142G    18K  legacy
    rpool/ROOT/opensolaris    2.37G   142G  2.24G  /
    rpool/dump                1019M   142G  1019M  -
    rpool/export                59K   142G    19K  /export
    rpool/export/home           40K   142G    19K  /export/home
    rpool/export/home/fsk141    21K   142G    21K  /export/home/fsk141
    rpool/swap                1019M   143G    16K  -
    

    This command shows pools/file systems. If you look you can see my two pools (nom, rpool) and the filesystems underneath the pools (ROOT, dump, export, swap)

    I would like to create subsets like the above (File Systems)

    root@Nom:/nom# zfs create nom/backup
    

    So now if I do a zfs list I get the following:

    root@Nom:/nom# zfs list
    NAME                       USED  AVAIL  REFER  MOUNTPOINT
    nom                       97.5K  1.78T    18K  /nom
    nom/backup                  18K  1.78T    18K  /nom/backup
    rpool                     4.36G   142G    72K  /rpool
    rpool/ROOT                2.37G   142G    18K  legacy
    rpool/ROOT/opensolaris    2.37G   142G  2.24G  /
    rpool/dump                1019M   142G  1019M  -
    rpool/export                59K   142G    19K  /export
    rpool/export/home           40K   142G    19K  /export/home
    rpool/export/home/fsk141    21K   142G    21K  /export/home/fsk141
    rpool/swap
    

    Since I'm going to be backing up to this file system I would like to turn on a couple little things... To get a listing of what zfs set can set then just type 'zfs set'

    root@Nom:/nom# zfs set compression=on nom/backup
    root@Nom:/nom# zfs set sharenfs=rw nom/backup
    

    I've just setup automagical compression, along with a read/write nfs share for '/nom/backup' Now all I need to do is setup nfs on my client machine to connect to the nfs server.

    Links:
    http://www.sun.com/bigadmin/features/articles/zfs_overview.jsp
    http://blogs.sun.com/timthomas/entry/creating_zfs_file_systems_from

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
esc
cancel