Displaying 3 results from an estimated 3 matches for "vdev_labels".
2012 Jan 11
0
Clarifications wanted for ZFS spec
...alid):
The value stored in offset is the offset in terms of
sectors (512 byte blocks). To find the physical block
byte offset from the beginning of a slice, the value
inside offset must be shifted over (<<) by 9 (2^9=512)
and this value must be added to 0x400000 (size of two
vdev_labels and boot block).
Does this calculation really go on in hard-coded 2^9
values, or in VDEV-dependant ashift values (i.e. 2^12
for 4k disks, 2^10 for default raidz, etc.)?
2) Likewise, in Section 2.6 (block size entries) the
values of lsize/psize/asize are said to be represented
by the number of 512...
2008 Jun 05
6
slog / log recovery is here!
(From the README)
# Jeb Campbell <jebc at c4solutions.net>
NOTE: This is last resort if you need your data now. This worked for me, and
I hope it works for you. If you have any reservations, please wait for Sun
to release something official, and don''t blame me if your data is gone.
PS -- This worked for me b/c I didn''t try and replace the log on a running
system. My
2013 Oct 26
2
[PATCH] 1. changes for vdiskadm on illumos based platform
...ind_best_root) {
@@ -1296,7 +1553,7 @@ zfs_mount(void)
stackbase = ZFS_SCRATCH;
stack = stackbase;
- ub_array = (uberblock_phys_t *)stack;
+ ub_array = stack;
stack += VDEV_UBERBLOCK_RING;
osp = (objset_phys_t *)stack;
@@ -1305,8 +1562,6 @@ zfs_mount(void)
for (label = 0; label < VDEV_LABELS; label++) {
- uint64_t sector;
-
/*
* some eltorito stacks don''t give us a size and
* we end up setting the size to MAXUINT, further
@@ -1324,39 +1579,38 @@ zfs_mount(void)
/* Read in the uberblock ring (128K). */
if (devread(sector +
- ((VDEV_SKIP_SIZE + VDEV_P...