Re: [BackupPC-users] BackupPC data on a Samba share

2008-04-26 Thread dan
yes, corruption can happen silently in the background! regular fsck can catch these while they are correctable or before they cause any major loss. ext3 and xfs have no mechanism for online fault correction to detect silent corruption. ZFS has this mechanism but I don't believe many people are

Re: [BackupPC-users] BackupPC data on a Samba share

2008-04-24 Thread David Rees
On Tue, Apr 22, 2008 at 8:31 AM, Stephen Joyce [EMAIL PROTECTED] wrote: For anything approaching 1TB or larger, consider xfs over ext3. Fsck'ing a large ext3 filesystem takes ages. Why would you ever need to fsck a ext3 volume? I suspect that a full fsck of an xfs volume is just as slow as

Re: [BackupPC-users] BackupPC data on a Samba share

2008-04-24 Thread Carl Wilhelm Soderstrom
On 04/24 03:10 , David Rees wrote: Why would you ever need to fsck a ext3 volume? Corruption happens. Especially if you have hardware that flakes out at all; which it might. -- Carl Soderstrom Systems Administrator Real-Time Enterprises www.real-time.com

[BackupPC-users] BackupPC data on a Samba share

2008-04-22 Thread shacky
Anyone is using BackupPC with the data directory (var/lib/backuppc) on a remote Samba share? I'm trying to do this but I have a lot of problems (like some timeout errors of smbclient in /var/log/messages). I wish to know if this configuration should work or if it is normal it to make me some

Re: [BackupPC-users] BackupPC data on a Samba share

2008-04-22 Thread Carl Wilhelm Soderstrom
On 04/22 04:43 , shacky wrote: Anyone is using BackupPC with the data directory (var/lib/backuppc) on a remote Samba share? Don't do it. - If you're using SMB or CIFS I don't think it will support the hardlinks that BackupPC requires for data pooling. - It's going to be slow. Just buy a big

Re: [BackupPC-users] BackupPC data on a Samba share

2008-04-22 Thread shacky
- If you're using SMB or CIFS I don't think it will support the hardlinks that BackupPC requires for data pooling. - It's going to be slow. Just buy a big cheap local disk. And connecting the external hard drive to a USB 2.0 port of the server formatting it to ext3? I cannot add another

Re: [BackupPC-users] BackupPC data on a Samba share

2008-04-22 Thread Carl Wilhelm Soderstrom
On 04/22 05:07 , shacky wrote: And connecting the external hard drive to a USB 2.0 port of the server formatting it to ext3? should work, tho not the fastest way to do things (and BackupPC is usually disk-speed-limited on modern hardware). -- Carl Soderstrom Systems Administrator Real-Time

Re: [BackupPC-users] BackupPC data on a Samba share

2008-04-22 Thread Nils Breunese (Lemonbit)
Carl Wilhelm Soderstrom wrote: On 04/22 04:43 , shacky wrote: Anyone is using BackupPC with the data directory (var/lib/backuppc) on a remote Samba share? Don't do it. - If you're using SMB or CIFS I don't think it will support the hardlinks that BackupPC requires for data pooling.

Re: [BackupPC-users] BackupPC data on a Samba share

2008-04-22 Thread Stephen Joyce
My opinion (worth exactly what you're paying for it): For anything approaching 1TB or larger, consider xfs over ext3. Fsck'ing a large ext3 filesystem takes ages. For portability, USB 2 is great. If the drive won't be moving and you have (or can add) the ports, consider Firewire, or better

Re: [BackupPC-users] BackupPC data on a Samba share

2008-04-22 Thread Tino Schwarze
On Tue, Apr 22, 2008 at 05:07:52PM +0200, shacky wrote: - If you're using SMB or CIFS I don't think it will support the hardlinks that BackupPC requires for data pooling. - It's going to be slow. Just buy a big cheap local disk. And connecting the external hard drive to a USB 2.0 port

Re: [BackupPC-users] BackupPC data on a Samba share

2008-04-22 Thread Daniel Denson
Quite simply, this is not possible using any kind of standard method. You could loopmount a ext3 disk image from the samba share but you will then be going through 2 software layers to get to the filesystem which will be quite slow! Best to get a NAS disk that supports NFS or to setup another