search for: volume_1

...oblems with english I ask for a friendly and a not too difficult answer. Using Windows 7 Pro, D-link DNS-323 NAS-Storage rSync: actual Version (just downloaded) Here is the stange behavier: I use rsync.exe -a -v --progress --delete --ignore-errors --force /cygdrive/N/ /cygdrive/ "//SPEICHER/Volume_1/Backup/10-er/D$/" So I want to backup the drive "N" from the Windows-Computer to //SPEICHER/Volume_1/Backup/10-er/D$/ on the NAS-Drive That works fine until all files are copied from "N" to //SPEICHER/Volume_1/Backup/10-er/D$/ After finishing that rSync starts to coppy A...

...them for secondary storage so only spin them up when I need them. My last access to the NAS was about a month ago before the upgrade to 4.10.2 The description of the drive within the "Configuration Your Computer" app on PCLOS is:/ / /?? Mount point: /mnt/DMediaV1 ?? Device: //dmedia/Volume_1 ?? Type: cifs ?? Options: vers=1.0,auto,user,username=%/ The fstab entry on the PCLOS machine for this unit is - ///dmedia/Volume_1 /mnt/DMediaV1 cifs vers=1.0,user,username=% 0 0/ which was created prior to the upgrade. The command used prior to the upgrade was "mount -t cifs //dmedia/...

...m up when I need them. > > My last access to the NAS was about a month ago before the upgrade to > 4.10.2 > > The description of the drive within the "Configuration Your Computer" > app on PCLOS is:/ > / > /?? Mount point: /mnt/DMediaV1 > ?? Device: //dmedia/Volume_1 > ?? Type: cifs > ?? Options: vers=1.0,auto,user,username=%/ > > The fstab entry on the PCLOS machine for this unit is - > ///dmedia/Volume_1 /mnt/DMediaV1 cifs vers=1.0,user,username=% 0 0/ > which was created prior to the upgrade. > > The command used prior to the up...

http://lists.gluster.org/pipermail/gluster-users/2018-April/033811.html On Tue, Apr 3, 2018 at 6:43 PM, Serg Gulko <s.gulko at gmail.com> wrote: > Hello! > > We are running distributed volume that contains 7 bricks. > Volume is mounted using native fuse client. > > After an unexpected system reboot, some files are disappeared from fuse > mount point but still available

Hello! We are running distributed volume that contains 7 bricks. Volume is mounted using native fuse client. After an unexpected system reboot, some files are disappeared from fuse mount point but still available on the bricks. The way it disappeared confusing me a lot. I can't see certain directories using ls -la but, at the same time, can cd into the missed directory. I can rename the