s3backer from fstab

[smbdiy]

This is a terrific product and it works like a champ from the command
line using:

s3backer --size=100g --blockSize=128k amazonS3bucket /mnt/s3backer

To date however I've had no luck configuring fstab.

Does this seem right ?

s3backer#amazonS3bucket /mnt/s3backer fuse size=100g,blockSize=128k 0
0

I have my amazon id and key defined in /root/.s3backer_passwd .

Thanks for any help.

[Archie Cobbs]

Here is what I have in my /etc/fstab. This seems to work. I've wrapped the long lines for readability...

# s3backer mount
s3backer#archiedisk /home/archie/mnt/s3b fuse
    noauto,size=1t,blockSize=256k,encrypt,compress=9,
    passwordFile=/home/archie/.s3backer_cryptkey,
    accessFile=/home/archie/.s3backer_passwd,prefix=backup1-,
    blockCacheSize=4000,blockCacheFile=/home/archie/mnt/cachefile,
    blockCacheWriteDelay=15000,blockCacheThreads=4,timeout=90
    0 0

# backup disk looped onto s3backer mount
/home/archie/mnt/s3b/file /home/archie/mnt/backup1 reiserfs
    noauto,loop,noatime,nodiratime
    0 0

Yours looks reasonable.. what error do you get?

-Archie

--
You received this message because you are subscribed to the Google Groups "s3backer-devel" group.
To post to this group, send email to s3backe...@googlegroups.com.
To unsubscribe from this group, send email to s3backer-deve...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/s3backer-devel?hl=en.

--
Archie L. Cobbs

[smbdiy]

Archie,

Thank you for your timely response. I've studied your fstab entry and
it certainly makes sense although it incorporates things I can only
hope to try in the future.

As regards my current situation I am using the amazon/fedora-8-i386-
v1.14-std (ami-84db39ed) EBS backed AMI.

I appreciate your question regarding an error and do not receive any
on the console - as important - I do not know where I would look for
errors thrown off by fstab.

If you can point me to a log of some sort I will take a look
immediately.

One question I do have: "Do I NEED to specifically reference
the .s3backer_passwd file in fstab".

Thank you again.

[Scott Lovenberg]

On 8/28/2010 1:11 PM, smbdiy wrote:
> If you can point me to a log of some sort I will take a look
> immediately.

Just a guess, but I'd think on Fedora you'll find mounting logs in
/var/log/messages as well as dmesg(8).

[Archie Cobbs]

On Sat, Aug 28, 2010 at 12:11 PM, smbdiy <smb...@gmail.com> wrote:

I appreciate your question regarding an error and do not receive any
on the console - as important - I do not know where I would look for
errors thrown off by fstab.

So how exactly are you determining that it's not working?
 

One question I do have: "Do I NEED to specifically reference
the .s3backer_passwd file in fstab".

No, you shouldn't.. but remember the default is relative to your home directory. So e.g. if you sudo to root, your $HOME could still be your normal user's home directory (depending on how sudo is configured).

-Archie

--
Archie L. Cobbs

[smbdiy]

Scott,

Thank you and when I looked in /var/log as you suggested the
"messages" and "dmesg" files were there.

Admittedly I am not sure what I am looking for however neither seems
to contain a string "s3backer" or "s3".

grep fuse does yield:
Aug 28 16:17:48 ip-10-202-54-205 kernel: fuse init (API version 7.8)

However no evidence of "file" or "stats" under /mnt/s3backer.

[smbdiy]

Archie,

When I issue the command:

s3backer --size=100g --blockSize=128k amazonS3bucket /mnt/s3backer

The aforementioned "file" and "stats" appear under /mnt/s3backer and
that is how I make my unscientific assessment that it is working ;-)

After which point it works nicely.

As I created my .s3backer_passwd in $HOME as root then I should be ok
there.

Thank you again for responding.

[Archie Cobbs]

On Sat, Aug 28, 2010 at 12:11 PM, smbdiy <smb...@gmail.com> wrote:

I appreciate your question regarding an error and do not receive any
on the console - as important - I do not know where I would look for
errors thrown off by fstab.

If you can point me to a log of some sort I will take a look
immediately.

The errors would be generated when you actually attempted to mount the partition. Just editing fstab doesn't do anything... you need to run the mount(8) command, which reads fstab, to actually ask the system to mount the filesystem.

In your case, try (as root) "mount /mnt/s3backer" and it should either work, or you should see some errors spit back out on the console.

-Archie

--
Archie L. Cobbs

[smbdiy]

Archie,

Thank you so much; I did exactly what you asked "try (as root) "mount /
mnt/s3backer"" and, yes, file and stats are immediately visible !

So, the entry in fstab was indeed working and now I am just wondering
how to automate the "mount /mnt/s3backer" command at startup ?

It seems from the example (next line) of your own fstab that when you
execute the second mount command for the "upper" file system that you
specify a filesystem (ie reiserfs).

/home/archie/mnt/s3b/file /home/archie/mnt/backup1 reiserfs
noauto,loop,noatime,nodiratime 0 0

In my case I would simply like to have it ready to go as the raw
"file" and "stats" with NO filesystem present and no blocks written to
S3.

Is that possible ?
If so would I do it in fstab or using some other method ?

Not sure if my good fortune with your most excellent guidance will
continue and I will keep my fingers crossed because we are almost
exactly where we need to be ;-)

[Archie Cobbs]

On Sun, Aug 29, 2010 at 3:21 PM, smbdiy <smb...@gmail.com> wrote:

So, the entry in fstab was indeed working and now I am just wondering
how to automate the "mount /mnt/s3backer" command at startup ?

Just remove the "noauto" flag.
 

It seems from the example (next line) of your own fstab that when you
execute the second mount command for the "upper" file system that you
specify a filesystem (ie reiserfs).

/home/archie/mnt/s3b/file /home/archie/mnt/backup1 reiserfs
noauto,loop,noatime,nodiratime 0 0

In my case I would simply like to have it ready to go as the raw
"file" and "stats" with NO filesystem present and no blocks written to
S3.

Then just don't add a second line in fstab. Then only the first will take effect.

 
-Archie

--
Archie L. Cobbs

[smbdiy]

Archie,

Uh oh; was not using the "noauto" flag and was using a single line...
Hmmm...

What follows is login as root and immediately issue four (4) commands

[root@ip-10-204-25-11 ~]# cat /etc/fstab
/dev/sda1 / ext3 defaults 1 1
/dev/mapper/swapVG-swapFS swap swap defaults 0 0
/dev/mapper/storageVG-storageFS /mnt ext3 defaults 0 0
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
s3backer#corilium /mnt/s3backer fuse size=100g,blockSize=128k 0 0
[root@ip-10-204-25-11 ~]# mount
/dev/sda1 on / type ext3 (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
none on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
[root@ip-10-204-25-11 ~]# mount /mnt/s3backer
s3backer: auto-detecting block size and total file size...
s3backer: auto-detection failed; using configured block size 128k and
file size 100g
[root@ip-10-204-25-11 ~]# mount
/dev/sda1 on / type ext3 (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
none on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
s3backer#http://s3.amazonaws.com/corilium/ on /mnt/s3backer type fuse
(rw,nosuid,nodev,allow_other,default_permissions)
[root@ip-10-204-25-11 ~]#

Sooo cloooose ;-)

[Archie Cobbs]

It looks like it's working fine. The "noauto" flag only applies at boot time.

-Archie

--
You received this message because you are subscribed to the Google Groups "s3backer-devel" group.
To post to this group, send email to s3backe...@googlegroups.com.
To unsubscribe from this group, send email to s3backer-deve...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/s3backer-devel?hl=en.

--
Archie L. Cobbs

[smbdiy]

Thank you so much for all of your help.

s3backer is a great product !