You are implying that the issues resulted from the H/W raid(s) and I don't
think that this is appropriate.
I configured a striped pool using two raids - this is exactly the same as using
two single hard drives without mirroring them. I simply cannot see what zfs
would be able to do in case of a
I think one has to accept that zfs send appearently is able to detect such
errors while scrub is not. scrub is operates only on the block level and makes
sure that each block can be read and is in line with its's checksum.
However, zfs send seems to have detected some errors in the file system
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of David Dyer-Bennet
>
> I must say that this concept of scrub running w/o error when corrupted
> files, detectable to zfs send, apparently exist, is very disturbing.
As previously mentioned, the
On Oct 6, 2010, at 1:26 PM, Stephan Budach wrote:
> Hi Cindy,
>
> thanks for bringing that to my attention. I checked fmdump and found a lot of
> these entries
>
> Okt 06 2010 17:52:12.862812483 ereport.io.scsi.cmd.disk.tran
...
> Okt 06 2010 17:52:12.862813713 ereport.io.scsi.cmd.disk.recov
I apologize if this has been covered before. I have not seen a blow-by-blow
installation guide for Ubuntu onto an iSCSI target.
The install guides I have seen assume that you can make a target visible to
all, which is a problem if you want multiple iSCSI installations on the same
COMSTAR targe
> "tb" == Thomas Burgess writes:
tb> I'm running b134 and have been for months now, without issue.
tb> Recently i enabled 2 services to get bonjoir notificatons
tb> working in osx
tb> /network/dns/multicast:default
tb> /system/avahi-bridge-dsd:default
tb> and i adde
Hello everybody.
I am experiencing terribly slow writes on my home server. This is from
zpool iostat:
capacity operationsbandwidth
pool alloc free read write read write
- - - - - -
On Fri, October 8, 2010 04:47, Stephan Budach wrote:
> So, I decided to give tar a whirl, after zfs send encountered the next
> corrupted file, resulting in an I/O error, even though scrub ran
> successfully w/o any erors.
I must say that this concept of scrub running w/o error when corrupted
fil
On 11 October, 2010 - Harry Putnam sent me these 0,5K bytes:
> Harry Putnam writes:
>
> [...]
>
> > I can't get X up ... it just went to a black screen, after seeing the
> > main login screen, logging in to consol and calling:
>
> WHOOPS, omitted some information here...
> Calling:
>
> `star
Harry Putnam writes:
[...]
> I can't get X up ... it just went to a black screen, after seeing the
> main login screen, logging in to consol and calling:
WHOOPS, omitted some information here...
Calling:
`startx /usr/bin/dbus-launch --exit-with-session gnome-session' from
console. Which is ho
Ian Collins writes:
[...]
>> I'm kind of having a brain freeze about this:
>> So what are the standard tests or cmds to run to collect enough data
>> to try to make a determination of what the problem is?
>>
>>
> Your motherboard manual would be the best place to look, it sounds
> like the B
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Harry Putnam
>
> beep beep beep beep beep beep
>
> I'm kind of having a brain freeze about this:
> So what are the standard tests or cmds to run to collect enough data
>
12 matches
Mail list logo
