Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to protect againts power failures #3

Open
HJarausch opened this issue May 20, 2018 · 2 comments
Open

How to protect againts power failures #3

HJarausch opened this issue May 20, 2018 · 2 comments

Comments

@HJarausch
Copy link

Hi,
I suffer from frequent power failures due to my fault-current circuit breaker.
In case of a power failure the file system which is cached by EnhanceIO I regularly loose data if not the directory structure itself.

Is there any means to protect oneself from this?

Many thanks for a hint,
Helmut

@tytgatlieven
Copy link

First of all: The first issue I would certainly try to tackle is the fault-current circuit breaker.
You will lose data and eventually the complete filesystem.
Do you have an idea about the reason? (A single PC may result in up to 10-20 mA fault-current, hence in europe 10+ PCs on a single breaker may become problematic.)
A UPS might also be a solution :-)

To answer the question:
I would assume that the reason for losing directory structure is due to the filesystem which has not yet flushed the data to disk.
Enhanceio is beneath the filesystem. In case there would be problems in enhanceio you would most likely get filesystem corruption.

@elmystico
Copy link
Owner

Great answer @tytgatlieven
@HJarausch you can try to change that circuitbraker to the less sensitive one- if that's possible (bigger fault-current). This is quite cheap to do. Think about the risk thou.
UPS is another choice that will fix your problems. Buy one linux-compliant of course, to allow shut-down if battery runs off.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants