Thanks, now I understand how the "CKSUM" is counted. Both fmdump and
scrub indicate that there is one error in the .vdi file.
Is there a way to enforce zfs to accept the new checksum of the file?
Since it is a hard drive image file I rather let the guest OS of the VM
handle that corruption (us
Hi,
what does not work for you on this MB?
Best regards,
Milan
On 20.02.2012 00:04, Hans J. Albertsson wrote:
What bios-setting should/must be used? And many more similar worries:
is there some paper or writeup or short note describing how to
generally set up normal motherboards to enable usi
Take a look at 'fmdump -eV' as it should give you more information about the
each of the checksum errors.
- George
On Feb 19, 2012, at 3:23 PM, Richard Lowe wrote:
> Vague recollection that the pool level is errors that weren't
> recovered, so possibly two of them on the device were ditto'd
> m
What bios-setting should/must be used? And many more similar worries: is
there some paper or writeup or short note describing how to generally
set up normal motherboards to enable using them with OI 151a? at least
partly?
___
OpenIndiana-discuss ma
Any idea where to find a 4TB drive with 512 byte sectors? Hitachis drives are
512b on 3TB, but AFAICS they have jumped to 4k sectors since the 4TB drives
came out
roy
- Opprinnelig melding -
> Umm, no, not all drives do this, it is relatively easy to get hold of
> drives that aren't EAR
Vague recollection that the pool level is errors that weren't
recovered, so possibly two of them on the device were ditto'd
metadata? (I'm very unsure on both counts).
Otherwise, as Chris said, iostat is particularly difficult to trust.
No matter what the error (even if, indeed, the drive or tran
On 02/19/12 08:42 AM, Anil Jangity wrote:
I just upgraded from 134b to 151a2. It seems there is a "r" flag (rename) under
Obsolete column. So, if the package was renamed, why do I still see this under old name?
Is there a way to clear them?
I am guessing this might be because there are some pa
I just upgraded from 134b to 151a2. It seems there is a "r" flag (rename) under
Obsolete column. So, if the package was renamed, why do I still see this under
old name? Is there a way to clear them?
I am guessing this might be because there are some packages that are dependent
on others, under
On 02/19/12 12:33, Robin Axelsson wrote:
What is conspicuous is that there are _no_ errors in iostat:
c2d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0
Today, I had a sudden corruption on the system disk/partition, or rather
the zfs partition where the image file of a VirtualBox VM is located
(i.e. not the rpool):
pool: systempool
state: ONLINE
status: One or more devices has experienced an error res
10 matches
Mail list logo
