Even with access to nice RAID controllers, I am now solidly in the software
(Linux only) RAID camp, unless you absolutely need the slight performance
increase in the hardware solution. The ability to yank the drives out and
put them into any computer, even one without a RAID controller is beyond
n
/sys should not be needed in a server unless you have a goofy NIC that
needs proprietary firmware ROM to work. I remove it from my servers without
issue.
/proc does not actually exist on the physical file system. It is a special
mount that maps to memory inside the running kernel and lets you see w
I like ext3/4 on top of LVM because I know it is very stable. I think I
will try ZFS on one server and stick with ext4 on LVM for the other. I know
that ext4 on LVM is fast enough to do what I need and the servers are
identical so I will be able to see how fast ZFS is.
The problem with why ZFS is
cron and dd with multiple sticks is a cool idea but can you use dd to image
a mounted filesystem? I've never tried it.
Thanks again, Dan
On Mon, Mar 26, 2012 at 6:52 AM, Royce Souther wrote:
> /sys should not be needed in a server unless you have a goofy NIC that
> needs proprietary firmware RO
You can use dd to read a mounted system but not write to it. Any files
being changed on the mounted one would end up corrupted on the none mounted
one. After dd has been run the first time rsync would work better. Mounting
the backup stick in /mnt and then using rsync to clone all the changes
ignor
Royce I really like this. I will dd an image onto another stick and update
it with cron and rsync. Its a plan!
Thanks man...
On Mon, Mar 26, 2012 at 9:49 AM, Royce Souther wrote:
> You can use dd to read a mounted system but not write to it. Any files
> being changed on the mounted one would en
On Mon, Mar 26, 2012 at 6:58 AM, Royce Souther wrote:
> I like ext3/4 on top of LVM because I know it is very stable. I think I
> will try ZFS on one server and stick with ext4 on LVM for the other. I know
> that ext4 on LVM is fast enough to do what I need and the servers are
> identical so I wi
On Mon, Mar 26, 2012 at 6:52 AM, Royce Souther wrote:
> /sys should not be needed in a server unless you have a goofy NIC that
> needs proprietary firmware ROM to work. I remove it from my servers without
> issue.
>
No, leave /sys alone. A lot more than that happens in /sys. See the
following:
Correct me if I'm wrong, but I don't believe FUSE is a viable option in
multi-user settings. I was looking at using sshfs to provide a network
share until I read that Fuse does not support file locking properly and
therefore could encounter problems when a file is being written to from
multipl
I have used ZFS extensively at home and at work for the last 5 years. My
advice is don't use ZFS on linux.
The fuse port is slow and you don't get some of the native OS features
of ZFS. I also can't speak to it's reliability. There is also a kernel
module built by 3rd party developers which wo
10 matches
Mail list logo
