@citrus-it in the past we've seen storage arrays that have zeroed out blocks
behind the scenes leading to ZFS reported checksums. We wanted to have a
default value that would not be confused with that type of corruption. We did
make this a global parameter (`zfs_initialize_value`) so that it cou
I know it's already integrated but the original description was about `zeroing`
out the unused blocks and the implementation actually writes `0xdeadbeef` which
makes it less useful for me in the case where I want to zero the blocks prior
to doing a hole-punch on a sparse VM disk (and I appreciat
Closed #586 via c3963210eb877c0bfb01c9ce117d0e7c1ac272e4.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/586#event-1595266956
--
openzfs: openzf
what is ti status of this PR?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/586#issuecomment-384447851
--
openzfs: openzfs-developer
Permalink:
@prakashsurya rebased.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/586#issuecomment-383088442
--
openzfs: openzfs-developer
Permalink:
https
@grwilson @ahrens Can either of you rebase this onto the latest master? The RTI
has been approved, but there's a small merge conflict. I'm happy to push once
it applies cleanly.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHu
@prakashsurya internal test link:
http://platform.jenkins.delphix.com/job/devops-gate/job/master/job/zfs-precommit/3168/flowGraphTable/
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/
Yes, @ahrens - I was incorrectly thinking of use case associated with
initializing physical blocks when disk is either TCG/SED drive, or God-forbid,
using some sort of RAID device in where there is already some sort of
logical/physical mapping.
* I did mention some parts of disk never getting
@dlethe I think you're thinking about a different use case than we are. We
want to avoid the first-write penalty on virtualized storage (e.g. ESX VMFS,
AWS EBS, etc). But perhaps your use case would also benefit from
initialization! Let me address a few of your specific points:
> The logic i
I don't see the practicality of this in most cases. The logic insures that a
pool will do unnecessary write I/Os on parts of the pool that certainly will
never get written to ... ever.
This will also not insure that all physical blocks even get initialized in the
first place. (you must not
@grwilson can you rebase this with the last master code when you get a chance?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/586#issuecomment-374339130
---
Igor K has also reviewed and tested this.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/586#issuecomment-374275520
--
openzfs: openzfs-develope
I think that @dcarosone is asking about creating a file in the pool to force
zfs to write to most of the pool (not dd-ing to the raw disk). That could work
but the `zpool initialize` approach has a few advantages:
- You don't need to figure out how big to make the file. The file size can't
b
You could go through and `dd` to every disk before adding it to the pool and
that is the common practice used by many. The problem that this is trying to
solve is to be able to avoid the delay of having to wait for every disk to be
pre-warmed before using it. Also, people often forget to "warm"
Why not just dd a file to a scratch dataset (with no compression, copies=3,
a suitable quota to prevent filling, and whatever other properties you
think might be relevant).
The use case is legitimate, but the need for more code to address it seems
dubious.
On Sat., 10 Mar. 2018, 13:11 George Wils
15 matches
Mail list logo
