Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
abstract:zfs-snapshots [2019/03/15 17:14]
frey [Accessing snapshots]
abstract:zfs-snapshots [2019/03/15 17:18] (current)
frey [Accessing a snapshot]
Line 39: Line 39:
 ===== Accessing a snapshot ===== ===== Accessing a snapshot =====
  
-Each snapshot under ''​.zfs/​snapshot''​ is itself a directory, which can be navigated from the filesystem using the standard Linux file system commands (like ''​cd''​ and ''​ls''​). ​ The files and directories present in the snapshot cannot be modified (''​rm''​ and ''​mv''​ will not work, neither will attempts to edit files in place), but they can be read (e.g. with ''​less''​or copied: +Each snapshot under ''​.zfs/​snapshot''​ is itself a directory, which can be navigated from the filesystem using the standard Linux file system commands (like ''​cd''​ and ''​ls''​). ​ The files and directories present in the snapshot cannot be modified (''​rm''​ and ''​mv''​ will not work, neither will attempts to edit files in place), but they can be read (e.g. with ''​less''​ or ''​head''​)
 <code bash> <code bash>
 [frey@login00 ~]$ ls -l ~/trace.txt [frey@login00 ~]$ ls -l ~/trace.txt
Line 46: Line 45:
 [frey@login00 ~]$ ls -l ~/​.zfs/​snapshot/​20190206-0115/​trace.txt [frey@login00 ~]$ ls -l ~/​.zfs/​snapshot/​20190206-0115/​trace.txt
 -rw-r--r-- 1 frey everyone 336436 Jan 25 09:39 /​home/​1001/​.zfs/​snapshot/​20190206-0115/​trace.txt -rw-r--r-- 1 frey everyone 336436 Jan 25 09:39 /​home/​1001/​.zfs/​snapshot/​20190206-0115/​trace.txt
 +[frey@login00 ~]$ head -5 ~/​.zfs/​snapshot/​20190206-0115/​trace.txt ​
 +#
 +# This file contains a code trace
 +# from a run of my program that is
 +# failing...
 +#
 +</​code>​
 +or copied to some writable location using ''​cp''​
 +<code bash>
 [frey@login00 ~]$ cp -a ~/​.zfs/​snapshot/​20190206-0115/​trace.txt ~/trace.txt [frey@login00 ~]$ cp -a ~/​.zfs/​snapshot/​20190206-0115/​trace.txt ~/trace.txt
 [frey@login00 ~]$ ls -l ~/trace.txt [frey@login00 ~]$ ls -l ~/trace.txt
 -rw-r--r-- 1 frey everyone 336436 Jan 25 09:39 /​home/​1001/​trace.txt -rw-r--r-- 1 frey everyone 336436 Jan 25 09:39 /​home/​1001/​trace.txt
-[frey@login00 ~]$ head ~/trace.txt  +[frey@login00 ~]$ head -5 ~/trace.txt  
-23128 execve("/​opt/​shared/​lumerical-fdtd/​2019a-R1/​bin/​fdtd-config-license",​ ["​fdtd-config-license"​],​ [/* 45 vars */]) = 0 +# 
-23128 brk(NULL) ​                        = 0x1400000 +# This file contains a code trace 
-23128 mmap(NULL, 4096, PROT_READ|PROT_WRITE,​ MAP_PRIVATE|MAP_ANONYMOUS,​ -1, 0) = 0x2b82dd5d4000 +# from a run of my program that is 
-23128 readlink("/​proc/​self/​exe",​ "/​opt/​shared/​lumerical-fdtd/​2019a"​...,​ 4096) = 59 +# failing... 
-23128 access("/​etc/​ld.so.preload",​ R_OK) = -1 ENOENT (No such file or directory) +# 
-23128 open("/​opt/​shared/​lumerical-fdtd/​2019a-R1/​bin/​../​lib/​tls/​x86_64/​libdl.so.2",​ O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) +</code>
-23128 stat("/​opt/​shared/​lumerical-fdtd/​2019a-R1/​bin/​../​lib/​tls/​x86_64",​ 0x7fffdc1789d0) = -1 ENOENT (No such file or directory) +
-23128 open("/​opt/​shared/​lumerical-fdtd/​2019a-R1/​bin/​../​lib/​tls/​libdl.so.2",​ O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) +
-23128 stat("/​opt/​shared/​lumerical-fdtd/​2019a-R1/​bin/​../​lib/​tls",​ 0x7fffdc1789d0) = -1 ENOENT (No such file or directory) +
-23128 open("/opt/​shared/​lumerical-fdtd/​2019a-R1/​bin/​../​lib/​x86_64/​libdl.so.2",​ O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)+
  • abstract/zfs-snapshots.1552670054.txt.gz
  • Last modified: 2019/03/15 17:14
  • by frey