[quick answers] ZFS Send backup

Joined
Oct 1, 2017
Messages
67
Thanks
0
#21
When I disconnect volume and then switch back then I will not touch it.
/mnt/Backup001

root@freenas:/mnt # cd Backup001
Backup001: Not a directory.

If the replication has finished and you don’t want to keep it incrementally backing up then sure you can just delete the snapshots.
Thanks have now removed them.
 

sretalla

FreeNAS Guru
Joined
Jan 1, 2016
Messages
768
Thanks
198
#22
You need to consider what may happen when you are backing up to the same host and holding copies of datasets on pools that are attached to the same host...

When you restart with both pools attached, the copies and the originals of every dataset have the same mountpoint set (usually like /mnt/pool1/dataset1...), so even if your backup of the dataset lives at pool2/backups/dataset1, the property of that dataset says its mountpoint is /mnt/pool1/dataset1...

Maybe some of you are already beginning to see what the problem is that I'm talking about here... both datasets want to be mounted in the same place and sometimes, the backup will be the one that gets there first.

So, what to do about that...

Well, you can set the property of the dataset (for EVERY individual/child dataset individually, since I don't think there's a zfs set -R option) called canmount to "noauto".

so like this:

zfs set canmount=noauto pool2/backups/dataset1

zfs set canmount=noauto pool2/backups/dataset1/child1

...


You can still mount those backup datasets manually with zfs mount...

Hope this helps to avoid a problem for somebody.
 

Apollo

FreeNAS Guru
Joined
Jun 13, 2013
Messages
831
Thanks
124
#23
You need to consider what may happen when you are backing up to the same host and holding copies of datasets on pools that are attached to the same host...

When you restart with both pools attached, the copies and the originals of every dataset have the same mountpoint set (usually like /mnt/pool1/dataset1...), so even if your backup of the dataset lives at pool2/backups/dataset1, the property of that dataset says its mountpoint is /mnt/pool1/dataset1...

Maybe some of you are already beginning to see what the problem is that I'm talking about here... both datasets want to be mounted in the same place and sometimes, the backup will be the one that gets there first.

So, what to do about that...

Well, you can set the property of the dataset (for EVERY individual/child dataset individually, since I don't think there's a zfs set -R option) called canmount to "noauto".

so like this:

zfs set canmount=noauto pool2/backups/dataset1

zfs set canmount=noauto pool2/backups/dataset1/child1

...


You can still mount those backup datasets manually with zfs mount...

Hope this helps to avoid a problem for somebody.
Not true.
Through replication from pool1 to pool2, pool 2 will have its own mountpoint and be treated as a single entity. The same goes for pool1.
 
Joined
Oct 1, 2017
Messages
67
Thanks
0
#24
Code:
14 April 2019 10:53 - Device: /dev/da14 [SAT], unable to open ATA device


zpool status
Code:
  pool: Backup001
 state: ONLINE
  scan: scrub repaired 0 in 0 days 04:36:29 with 0 errors on Mon Apr 15 02:02:29 2019
config:

        NAME                                          STATE     READ WRITE CKSUM
        Backup001                                     ONLINE       0     0     0
          gptid/e52e6d36-3230-11e9-a118-3cfdfea22e66  ONLINE       0     0     0

errors: No known data errors

  pool: Store2
 state: ONLINE
  scan: scrub repaired 0 in 0 days 09:21:48 with 0 errors on Sun Mar 17 09:21:49 2019
config:

        NAME                                                STATE     READ WRITE CKSUM
        Store2                                              ONLINE       0     0     0
          mirror-0                                          ONLINE       0     0     0
            gptid/9d17bcbc-066b-11e8-b8a8-0cc47a5808e8.eli  ONLINE       0     0     0
            gptid/9df33389-066b-11e8-b8a8-0cc47a5808e8.eli  ONLINE       0     0     0
          mirror-1                                          ONLINE       0     0     0
            gptid/a03134f9-066b-11e8-b8a8-0cc47a5808e8.eli  ONLINE       0     0     0
            gptid/a0f17bac-066b-11e8-b8a8-0cc47a5808e8.eli  ONLINE       0     0     0
          mirror-2                                          ONLINE       0     0     0
            gptid/a3334340-066b-11e8-b8a8-0cc47a5808e8.eli  ONLINE       0     0     0
            gptid/a3f64588-066b-11e8-b8a8-0cc47a5808e8.eli  ONLINE       0     0     0
          mirror-4                                          ONLINE       0     0     0
            gptid/5d4a0fd3-1312-11e8-b729-0cc47a5808e8.eli  ONLINE       0     0     0
            gptid/5e12941f-1312-11e8-b729-0cc47a5808e8.eli  ONLINE       0     0     0
          mirror-5                                          ONLINE       0     0     0
            gptid/612876f0-1312-11e8-b729-0cc47a5808e8.eli  ONLINE       0     0     0
            gptid/61eacf52-1312-11e8-b729-0cc47a5808e8.eli  ONLINE       0     0     0
          mirror-6                                          ONLINE       0     0     0
            gptid/65096079-1312-11e8-b729-0cc47a5808e8.eli  ONLINE       0     0     0
            gptid/65d19969-1312-11e8-b729-0cc47a5808e8.eli  ONLINE       0     0     0
        logs
          mirror-3                                          ONLINE       0     0     0
            gptid/a4d713ca-066b-11e8-b8a8-0cc47a5808e8.eli  ONLINE       0     0     0
            gptid/a549c4e3-066b-11e8-b8a8-0cc47a5808e8.eli  ONLINE       0     0     0

errors: No known data errors

  pool: freenas-boot
 state: ONLINE
  scan: scrub repaired 0 in 0 days 00:00:07 with 0 errors on Sun Apr 14 03:45:07 2019
config:

        NAME        STATE     READ WRITE CKSUM
        freenas-boot  ONLINE       0     0     0
          mirror-0  ONLINE       0     0     0
            da12p2  ONLINE       0     0     0
            da13p2  ONLINE       0     0     0

errors: No known data errors


smartctl -a /dev/da14
Code:
smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.1-STABLE amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate IronWolf
Device Model:     ST8000VN0022-2EL112
Serial Number:    ZA1E0723
LU WWN Device Id: 5 000c50 0b3afcabc
Firmware Version: SC61
User Capacity:    8,001,563,222,016 bytes [8.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Apr 15 10:08:09 2019 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (  567) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 785) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x50bd) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   100   065   044    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0003   092   092   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       4
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   076   060   045    Pre-fail  Always       -       39611142
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       1378
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       4
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   063   059   040    Old_age   Always       -       37 (Min/Max 34/39)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       1379
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       4
193 Load_Cycle_Count        0x0032   099   099   000    Old_age   Always       -       2680
194 Temperature_Celsius     0x0022   037   041   000    Old_age   Always       -       37 (0 25 0 0 0)
195 Hardware_ECC_Recovered  0x001a   100   006   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       1375 (141 204 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       15837143116
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       5626008547

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
 
Joined
Oct 1, 2017
Messages
67
Thanks
0
#25
Is this hard drive severely damaged? This is not the backup disk.

29 Mars 2019 05:27 - Device: /dev/da10 [SAT], 8 Currently unreadable (pending)

Code:
smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.1-STABLE amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Gold
Device Model:     WDC WD6002FRYZ-01WD5B0
Serial Number:    K1JS0SHD
LU WWN Device Id: 5 000cca 255e6a663
Firmware Version: 01.01M02
User Capacity:    6,001,175,126,016 bytes [6.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Apr 15 10:11:06 2019 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (  113) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 870) minutes.
SCT capabilities:              (0x003d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   138   138   054    Pre-fail  Offline      -       100
  3 Spin_Up_Time            0x0007   100   100   024    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       4
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   128   128   020    Pre-fail  Offline      -       18
  9 Power_On_Hours          0x0012   099   099   000    Old_age   Always       -       11368
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       4
192 Power-Off_Retract_Count 0x0032   099   099   000    Old_age   Always       -       2222
193 Load_Cycle_Count        0x0012   099   099   000    Old_age   Always       -       2222
194 Temperature_Celsius     0x0002   130   130   000    Old_age   Always       -       46 (Min/Max 24/54)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       8
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
 

sretalla

FreeNAS Guru
Joined
Jan 1, 2016
Messages
768
Thanks
198
#26
Pending sectors aren't good.

The other error looks like a dropout (brown-out) of either disk or controller... is your power supply close to its limit?
 

sretalla

FreeNAS Guru
Joined
Jan 1, 2016
Messages
768
Thanks
198
#27
Not true.
Through replication from pool1 to pool2, pool 2 will have its own mountpoint and be treated as a single entity. The same goes for pool1.
Perhaps you're right that I'm remembering this more specifically from a case with the /mnt/iocage mountpoint that's special to datasets related to iocage jails.

I never said the pools don't have independent mountpoints. If the dataset is replicated as-is, the property of mountpoint will remain as set on the original... I haven't been able to do a test yet to confirm what happens, but I guess some more people would have noticed and complained about it if it caused mount conflicts (or maybe there are people writing live to their backups without knowing it... I only noticed because my jails... on SSD... were running really slow after a reboot, which turned out to be that they were running off the spinning disk backup instead... I am aware that the replicas are set to read-only mounts by default, so perhaps I'm just imagining it all).
 
Joined
Oct 1, 2017
Messages
67
Thanks
0
#28
Pending sectors aren't good.

The other error looks like a dropout (brown-out) of either disk or controller... is your power supply close to its limit?
Successful access to the one I update to a newer version and seem to work now.

Edit: It has access to 1 840 watts (920 x 2).

But now I have a bigger problem I create a new thread for it so that there will be no misunderstanding,
https://www.ixsystems.com/community/threads/acute-problem-problem-with-the-hard-drive.75679/
 
Last edited:

Apollo

FreeNAS Guru
Joined
Jun 13, 2013
Messages
831
Thanks
124
#29
Perhaps you're right that I'm remembering this more specifically from a case with the /mnt/iocage mountpoint that's special to datasets related to iocage jails.

I never said the pools don't have independent mountpoints. If the dataset is replicated as-is, the property of mountpoint will remain as set on the original... I haven't been able to do a test yet to confirm what happens, but I guess some more people would have noticed and complained about it if it caused mount conflicts (or maybe there are people writing live to their backups without knowing it... I only noticed because my jails... on SSD... were running really slow after a reboot, which turned out to be that they were running off the spinning disk backup instead... I am aware that the replicas are set to read-only mounts by default, so perhaps I'm just imagining it all).
I think I now understand what you mean.
If you were to replace pool1 with pool2, while both pools are identical the change of the pool name alone is going prevent iocage to be properly run because their mapping is based on the pool1 name.
An export (renaming) of pool2 into pool1 followed by an import should fix it assuming the pool is not encrypted.
For that particular reason, it is often preferable to replicate over LAN to another Freenas box. That way, both Freenas box can use the same pool name without interference.
 
Top