<div dir="ltr"><div>Call me stupid, but I forgot we were talking about ZFS on Linux... you're right. No <i>fstab</i> and no <span class=""><em>vfstab</em>.<br></span></div><div><span class="">Sorry about that.<br><br></span></div>
<span class="">-> Jake<br></span></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Mar 11, 2014 at 3:01 PM, Jeremy MountainJohnson <span dir="ltr"><<a href="mailto:jeremy.mountainjohnson@gmail.com" target="_blank">jeremy.mountainjohnson@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Not sure on the distro you have, but with ZFSonLinux you don't use fstab. For example, in Arch there is a service to handle this if enabled at boot (part of the zfs package). The file system mount point is configured with zfs user space tools, or defaults to what you set originally when you created the volume.<br>
<br></div>Also, curious on the ram problems. Arch, the distro I use, is tweaked to be heavy on caching to RAM. So, often times when I am working with extensive I/O and large files, 90% of memory will be dedicated to caching in RAM and never touch swap (ext4, sw raid1). If I need that cached RAM, it diverts it out of the cache automatically. The free command shows how RAM is allocated. I'm no zfs expert, but perhaps zfs is caching like crazy to RAM, although now that you're stable with more RAM, this kinda debunks that. <br>
<br></div><div class="gmail_extra"><br clear="all"><div>--<br>Jeremy MountainJohnson<br><a href="mailto:Jeremy.MountainJohnson@gmail.com" target="_blank">Jeremy.MountainJohnson@gmail.com</a></div><div><div class="h5">
<br><br><div class="gmail_quote">On Tue, Mar 11, 2014 at 2:42 PM, <span dir="ltr"><<a href="mailto:tclug@freakzilla.com" target="_blank">tclug@freakzilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Course I'm not using ECC RAM. This is a home system (:<br>
<br>
The data is... well, be nice if it didn't get corrupted, but if a video file gets a small glitch in it, it's not a huge deal. I can always rerip one disc if I need to. I also figured that's why I have two smaller raidz1 (which is equivalent to raid5, right?) pools - it should be able to fix the occasional checksum error.<br>
<br>
I've not seen any crop up on this setup until that scrub, which was after I copied and erased about 8TB a couple of times. So not super worried.<br>
<br>
I can't really not use the filesystem during a scrub, since a scrub takes over 24 hours. I could restrict it to read-only.<br>
<br>
Hey, that reminds me, for some reason the thing mounts as read-only when I reboot. And since it's not in fstab I don't know where to fix that... anyone?...<div><div><br>
<br>
<br>
<br>
On Tue, 11 Mar 2014, Jake Vath wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Now, I am seeing occasional checksum errors. I stress-tested the<br>
heck out of the thing for a week or so (filled up the<br>
filesystem, then deleted most the junk I used for that, etc) and<br>
when I ran a scrub it found 12 of them. I'm assuming that since<br>
I am running multiple redundancies that that's not a huge<br>
problem. Is this correct? Should I cronjob a scrub once a month?<br>
<br>
Are you using ECC RAM?<br>
If you're not, then you'll see some checksumming/parity calculation errors.<br>
Is this a huge problem? I guess it could be when you consider how important<br>
your data is to you.<br>
Your ZPool(s) could get really screwed up if you're getting checksumming<br>
errors.<br>
<br>
A cronjob to scrub the system isn't a bad idea, I guess you'd have to make<br>
sure that nothing is going to try and use the system during the scrubbing<br>
process though.<br>
<br>
-> Jake<br>
<br>
<br>
-> Jake<br>
<br>
<br>
On Tue, Mar 11, 2014 at 2:24 PM, <<a href="mailto:tclug@freakzilla.com" target="_blank">tclug@freakzilla.com</a>> wrote:<br>
This is a follow-up to my ZFS woes from a month or so ago.<br>
<br>
Funny thing. When that machine had 16gigs of RAM + 16gigs of<br>
swap, it was using 15gig of RAM and not touching swap at all,<br>
and ZFS performace was horrible.<br>
<br>
So I threw another 16gigs of RAM in there.<br>
<br>
Now it uses 20gigs of RAM (still not touching swap, obviously)<br>
and ZFS performance is fine.<br>
<br>
Now, I am seeing occasional checksum errors. I stress-tested the<br>
heck out of the thing for a week or so (filled up the<br>
filesystem, then deleted most the junk I used for that, etc) and<br>
when I ran a scrub it found 12 of them. I'm assuming that since<br>
I am running multiple redundancies that that's not a huge<br>
problem. Is this correct? Should I cronjob a scrub once a month?<br>
<br>
I'm pretty gald I didn't need to move away from ZFS...<br>
<br>
--<br>
______________________________<u></u>_________________<br>
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br>
<a href="mailto:tclug-list@mn-linux.org" target="_blank">tclug-list@mn-linux.org</a><br>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list" target="_blank">http://mailman.mn-linux.org/<u></u>mailman/listinfo/tclug-list</a><br>
<br>
<br>
<br>
<br>
</blockquote>
______________________________<u></u>_________________<br>
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br>
<a href="mailto:tclug-list@mn-linux.org" target="_blank">tclug-list@mn-linux.org</a><br>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list" target="_blank">http://mailman.mn-linux.org/<u></u>mailman/listinfo/tclug-list</a><br>
</div></div></blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br>
<a href="mailto:tclug-list@mn-linux.org">tclug-list@mn-linux.org</a><br>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list" target="_blank">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a><br>
<br></blockquote></div><br></div>