i am moving folders from server into another debian -> centos using sftp .
the folders size is different after the transfer is done . for example :
remote server :
sftp 00.00.00
sftp get folderName ( size 87mb)
on local server :
du -sh *
folderName ( size 83mb )
is it possible i am not transferring the hidden files and folders?
I'm used to consider that USB transfers are safe for data, that is USB does not add level of unreliability to data storage.
However, I read that USB is not always a good choice for data transfer concerning its reliability. For instance, It seems that using USB disk in a RAID is not a good idea.
I would like to know if the risk of data loss is specific to the way RAID works, or is intrinsic to every USB transfer.
I need to replace the HDD on a single disk system used as a pbx (CentOS-6 based FreePBX). The existing partition structure is:
ls -l /dev/sd*
brw-rw---- 1 root disk 8, 0 Apr 17 2018 /dev/sda
brw-rw---- 1 root disk 8, 1 Apr 17 2018 /dev/sda1
brw-rw---- 1 root disk 8, 2 May 25 14:12 /dev/sda2
parted /dev/sda print
Model: ATA ST3500418AS (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 525MB 524MB primary ext4 boot
2 525MB 500GB 500GB primary lvm
parted /dev/sda1 print
Model: Unknown (unknown)
Disk /dev/sda1: 524MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 524MB 524MB ext4
parted /dev/sda2 print
Error: /dev/sda2: unrecognised disk label
I need to transfer the entire system to a new HDD. Ideally I would like to transfer the entire thing (boot-loader, OS, and filesystems) over the network to a larger disk temporarily installed on a separate host, that is not necessarily running CentOS, and then swap the drives. Is this possible?
I am guessing that with lvm in the mix this is a non-starter. But in case it is not then this scenario is the ideal.
Is this possible and how is it best accomplished?
Further information:
df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/vg_voinet01-lv_root
64376668 5057112 56042756 9% /
tmpfs 1952596 0 1952596 0% /dev/shm
/dev/sda1 487652 55768 406284 13% /boot
/dev/mapper/vg_voinet01-lv_home
3159816 246372 2749604 9% /home
/dev/mapper/vg_voinet01-LogVol04
322407500 134244852 171778648 44% /var
/dev/mapper/vg_voinet01-lv_log
9545056 390052 8663484 5% /var/log
/dev/mapper/vg_voinet01-lv_spool
65924860 32354984 30214852 52% /var/spool
vgs;lvs
VG #PV #LV #SN Attr VSize VFree
vg_voinet01 1 6 0 wz--n- 465.27g 9.91g
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
LogVol04 vg_voinet01 -wi-ao---- 312.50g
lv_home vg_voinet01 -wi-ao---- 3.12g
lv_log vg_voinet01 -wi-ao---- 9.38g
lv_root vg_voinet01 -wi-ao---- 62.50g
lv_spool vg_voinet01 -wi-ao---- 64.00g
lv_swap vg_voinet01 -wi-ao---- 3.86g
Keep in mind, both machines used are hosted in a Proxmox Node.
SETUPS
My Samba setup is installed on Ubuntu inside an LXC. The shares are located on a RAIDZ2 dataset, and are accessible from the LAN. 4 LCores, 6 GB RAM
The Windows 10 VM is on a different physical SSD from the LXC. It is on the same network as the Ubuntu LXC and both are connected to the same virtual switch (iperf shows a bandwidth of around 15.9 Gbits/sec). 4 LCores, 8 GB RAM
SCENARIO
I open a VNC console to the Windows 10 machine and login to the Samba share through explorer. I select a file over 2 GB and it starts to transfer the file. Initially, the transfer will start at like 255 MB/s (fast), but then it will slow down to 0MB/s within 5 seconds of starting the transfer. After the initial drop, the transfer will top out at only 5 MB/s for the rest of the time, while occasionally dipping down to 0.
I suspect something can’t keep up and do not know if it is a physical hardware issue or a virtual one.
Is there anything that I should check/change to get consistent samba speeds?
I'm trying to create a master/slave setup using NSD. I have NSD installed on two servers. The servers are running great; when I perform normal DNS queries they return the information from the zone files. However, when I try to nsdc notify on the master, the slave doesn't seem to pick up the new zone configuration.
The nsd.conf file on the master looks like this:
## NSD authoritative only DNS
#
server:
logfile: "/var/log/nsd.log"
port: 53
server-count: 1
ip4-only: yes
hide-version: yes
identity: ""
zonesdir: "/etc/nsd3"
verbosity: 3
zone:
name: domain.com
zonefile: www.domain.com.forward
notify: <ip slave> NOKEY
provide-xfr: <ip slave> NOKEY
nsd.conf on the slave server looks like:
## NSD authoritative only DNS
#
server:
logfile: "/var/log/nsd.log"
port: 53
server-count: 1
ip4-only: yes
hide-version: yes
identity: ""
zonesdir: "/etc/nsd3"
verbosity: 3
zone:
name: domain.com
zonefile: www.domain.com.forward
allow-notify: <ip master> NOKEY
request-xfr: AXFR <ip master> NOKEY
The zonefile file looks like this on the master server:
$ORIGIN domain.com.
$TTL 86400 ; default time to live
@ IN SOA ns1.domain.com. admin.domain.com. (
2011010203 ; serial number
28800 ; Refresh
7200 ; Retry
864000 ; Expire
86400 ; Min TTL
)
NS ns1.domain.com.
MX 10 mailfilter.hostingprovider.com.
mail IN A <ip mailserver hostingprovider>
www IN A <ip master>
ns1 IN A <ip master>
ns2 IN A <ip slave>
newvalue IN A 8.8.8.8
* IN A <ip master>
The forward file is the same on the slave server, except for the line with "newvalue" (the value I want to transfer).
If I perform a nsdc notify on the master server, the following ends up in the slave's logs:
[1487507948] nsd[26038]: info: Notify received and accepted, forward to xfrd
[1487507948] nsd[26037]: info: Handle incoming notify for zone domain.com
However, the zone files don't seem to get updates. After the notify, I perform nsdc patch; nsdc rebuild; nsdc reload; service nsd3 restart on the slave server, just to be sure. But this doesn't change the zone files either.
Also, if I perform a dig axfr @<master ip> domain.com on the slave server, I get a nice zone transfer.
Why isn't the slave server updating the zone files?