No, it installs. It's just that files won't be backed up until CrashPlan does a scan of the file system, which doesn't happen frequently as it can take a long time to do so, especially with a lot of files to look at and compare against. Normally CrashPlan will back up changed files every 15 minutes, so you're insured of a backup. I've had scans that take over 1 hour to complete. Also, CrashPlan has versioning of backed up files, which can be put "at risk" if they aren't backed up except when a full scan is initiated.
So, no, the value doesn't have to be increased. However, CrashPlan's utility is degraded without that feature. And, yes, I've actually had to use that capability before :). John Sent from my iPad > On Oct 13, 2015, at 7:20 PM, Nigel W <[email protected]> wrote: > > I am not sure that limit matters in this case. Is this preventing you from > installing CrashPlan? > > Reading the page, the inotify option is for detecting that files have changed > in realtime. Unless you are backing up the contents of the LX zone and you > require the realtime backup functionality, you don't need the inotify > features. > >> On Tue, Oct 13, 2015 at 11:09 AM, John Croix <[email protected]> wrote: >> So I guess I'm a little unclear. The way that the statement was phrased (if >> you absolutely must tune it) implies that there are negative ramifications >> associated with setting the value for the system. At 1.5M files instead of >> 8K, is this something that's going to severely impact the performance of the >> host system? Like I said, I *could* create a KVM which, I believe, would >> solve the problem. I just don't want to because of the additional memory and >> CPU overhead associated with a KVM. I'd much rather stick with a LX-branded >> zone, if at all possible. >> >> Thanks, >> John >> >>> On Oct 12, 2015, at 07:14 PM, John Croix <[email protected]> wrote: >>> >> >>> CrashPlan's example was 1M. I checked my backup status, and I'm at over 1M >>> files, so I was going to do 1.5M. >>> >>> Here's an article on the problem as CrashPlan explains it. >>> >>> John >>> >>>> On Oct 12, 2015, at 06:47 PM, Bryan Cantrill <[email protected]> >>>> wrote: >>>> >>> >>>> >>>> We don't currently allow this value to be tuned via LX /proc, but if you >>>> absolutely must tune it, you can tune inotify_maxwatches to a higher >>>> number via /etc/system on the host (or via mdb -kw, if you'd prefer to not >>>> reboot). >>>> >>>> It's not impossible for us to make this tunable on a per-zone basis, we >>>> just didn't bother because we didn't think apps were depending on it. >>>> What is CrashPlan trying to set it to? >>>> >>>> - Bryan >>>> >>>> >>>>> On Mon, Oct 12, 2015 at 4:37 PM, John Croix <[email protected]> wrote: >>>>> I’m trying to run CrashPlan in a LX-branded zone. I’m using the 5 Oct >>>>> 2015 Ubuntu LX-image (52be84d0-6b06-11e5-a4c0-9f0c52fa368a). Everything >>>>> installs OK, but I get a message from the CrashPlan installer saying that >>>>> I need to increase the maximum number of watched files in Linux, which >>>>> defaults to 8192. To do so, I need to set the value of >>>>> fs.inotify.max_user_watches in /etc/sysctl.conf. I’ve done this and >>>>> rebooted the VM, but the value still shows up at 8192 when I cat >>>>> /proc/sys/fs/inotify/max_user_watches. >>>>> >>>>> Does anybody know how I can change this value? I’d prefer to stick with a >>>>> LX-branded zone rather than to go to a KVM, if at all possible. >>>>> >>>>> Thanks, >>>>> John >>>>> >>>> > > smartos-discuss | Archives | Modify Your Subscription ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
