Beiträge von Davy39

Hi,
I guess I'm talking about rsync plugin, I mean OMV rsync job tasks from service panel.
You're right, there is no problem with spaces in sub-folders, only with the root folder of the shared folders selected (source & destination).

Hi,
As often with Linux, I'm facing some problems with space in folder names. I know, spaces are bad, but I would prefer not to modify my directory structure...
I would like to make a copy between shared folders whose name contains spaces like "My music folder".
When I try to rsync those folders, I'm getting an error since OMV apparently does not escape spaces ("My\ music\ folder") and try to reach "My" folder which obviously doesn't exist...
Is there a trick to do it or should I report this in OMV bugtracker ?
Thanks

OK, I'm going report this there. Thanks.

Hi,
After my first OMV installation, I noticed an annoying cranking from my HDD every second. I was even afraid that there may have been damaged during transportation...
Using iotop, I realized it was coming from ext4lazyinit process.
After a look on internet, I learned that it was coming from the way ext4 formating is done by default... it takes days to be finished !
This annoying behaviour could be override by using lazy_itable_init=0,lazy_journal_init=0 parameters for mkfs.
It takes a little longer, but then the file system initialisation is definitively done.

What do you think about that being default OMV behaviour, or at least an option ?

Thanks, I got it now !
It works with default configuration of OMV and the simplest autofs config :
MyFolder -fstype=nfs,rw 192.168.1.10:/export/MyFolder

I guess my problems were first coming from imbrication of shared folders and owncloud...
I'm gonna try reset this in a more proper way
We always think it is more complicated than it really is...
I will set this treat as solved in a couple of days if I have no more problem.
Anyway, thanks !

Thanks for reply.
If I understand your point, since my client user on my lapop (linux mint) is part of users group (gid=100), it should theoretically be able to access the nfs shared folder as long as its ACL is 775, and that without modifying any NFS option.
Is that right ?
I'm going to try again on a fresh and cleaner install.
Will keep in touch

OK, thanks !
So I guess few Mo everyday is great for saving my usb key lifetime.
Thanks for your work.

Hi,
I just set up my first NAS and have some problems with sharing via NFS.
I'm pretty used to work with debian/ubuntu/mint OS as my laptop and desktop system.
However, these are my first steps about NFS sharing... and it really drives me crazy !

I try to access to my nfs shared folders with my linux mint OS and autofs... sometimes it works and sometimes (after reboot and/or writing on it) won't work anymore !
I guess it's due to /etc/auto.nfs (client) and /etc/export (server) options, but I didn't get to a working and stable configuration yet.
Maybe I shoud precise that I'm able to see shared folders (showmount -e), to mount them, but not to access to it (read or write).

Here are some questions which hopefully may help be to go on :

OMV NFS config :
1- Do I have to change the default parameters on OMV (ie insecure, no_subtree_check) ?
2- Do I have to add some more on the server side (anonuid=, anongid=,root_squash,no_root_squash,all_squash) ?
3- Should I restart nfs-kernel-server after changes ?

OMV shared folder config :
4 - What should be priviledges and ACL for owner/group/others for the shared folder ?
5 - What about sub-folders ?
6 - Should I restart nfs-kernel-server or anything else after changes ?

Client autofs config :
7 - Should I specify some options in /etc/auto.nfs (uid,gid...) ?
8 - Should I restart autofs to apply changes ?

Many thanks for your help !

Edit : I've tryed to simplify my setup in order to avoid potential sources of problems. And for now it works...
- I've disabled owncloud and related shared folders
- I've disabled a shared folder containing the one I wanted to access
It looks like this permission issue could be very tricky some times...

Thanks ryecoaaron for this quick and comforting reply.
I 'm not yet aware of the details of your plugin... for a better understanding what do you mean by the "data written display" ?
Thanks

Edit : I've edited /etc/openmediavault/config.xml as you suggested, and after reboot "root" is "/dev/sde1" and "write kbyte" seems now activated. Good... even if I don't know what it means

Hi everyone,
I'm glad to be a new member of your community
I recently build my first NAS with a Q1900-ITX board, a 12V-8A picoPSU, 4x 4To WD blue HDD (using idle3-tools to disable head parking) and recycled 4Go ram from old laptop.
I've made a ext4 partition on top of luks encrypted RAID5. Openmediavault seems to work like a charm, I think I'm going to adopt it

Since I've decided to install the system on a USB key for now (maybe I'll upgrade to msata in the future), I wanted to install flash memory plugin.
I've done the manual modifications of /etc/fstab as adviced by the plugin.
I rebooted without problem, however I'm not sure it's well configured :

The plugin configuration page give me "root : /dev/sda1" but my root drive change to sde since the installation.

Is that a problem ? Is there a way to manually change this configuration ?

Thanks for your help