On 8/11/07, Stan Seibert <[EMAIL PROTECTED]> wrote:
> I'm not sure if that answers the question you were asking, but generally I
> found that damage to a zpool was very well confined.
But you can't count on it. I currently have an open case where a
zpool became corrupt and put the system into a
Thanks for the info folks.
In addition to the 2 replies shown above I got the following very
knowledgeable reply from Jim Dunham (for some reason it has not shown up here
yet so I'm going to paste it in).
Chris,
For the purposes of isolating corruption, the separation of two or more
Hello everyone, I am slowly running out of space in my zpool.. so I wanted to
replace my zpool with a different zpool..
my current zpool is
> zpool list
NAMESIZEUSED AVAILCAP HEALTH ALTROOT
mypool 278G263G 14.7G94% ONLINE -
> zp
Chris,
> In the old days of UFS, on occasion one might create multiple file
> systems (using multiple partitions) of a large LUN if filesystem
> corruption was a concern. It didn’t happen often but filesystem
> corruption has happened. So, if filesystem X was corrupt
> filesystem Y woul
I did some tests with zfs-fuse where I created a pool with two vdevs (no mirror
or raid-z) and filled it up with files. Then I deliberately corrupted bytes on
the vdev and scrubbed the pool to see what happened. ZFS was able to pinpoint
exactly which files were corrupted and reported their ful
On 8/11/07, Russ Petruzzelli <[EMAIL PROTECTED]> wrote:
>
> Is it possible/recommended to create a zpool and zfs setup such that the OS
> itself (in root /) is in its own zpool?
Yes. You're looking for "zfs root" and it's easiest if your installer
does that for you. At least latest nexenta unsta
Is it possible that a faulty disk controller could cause corruption to a
zpool? I think I had this experience recently when doing a 'zpool replace'
with both the old/new device attached to a controller that I discovered was
faulty (because I got data checksum errors, and had to dig for backups).
> In the old days of UFS, on occasion one might create
> multiple file systems (using multiple partitions) of
> a large LUN if filesystem corruption was a concern.
> It didn’t happen often but filesystem corruption
> has happened. So, if filesystem X was corrupt
> filesystem Y would be just fine
In the old days of UFS, on occasion one might create multiple file systems
(using multiple partitions) of a large LUN if filesystem corruption was a
concern. It didn’t happen often but filesystem corruption has happened. So,
if filesystem X was corrupt filesystem Y would be just fine.
With Z
