Hi,
Great stuff.
Does this change will make it into opensolaris? Looking at actual code I
couldn't find the modification.
I try to replace zdb.c in the opensolaris main tree before compiling with
nightly but the compiler wasn't happy with it. Can you write down the right
options?
bbr
I don't think that this is hardware issue, however i don't except this. I'll
try to explain why.
1. I've replaced all memory modules which are more likely to cause such a
problem.
2. There are many different applications running on that server (Apache,
PostgreSQL, etc.). However, if you look
I 'm trying to decode a lzjb compressed blocks and I have some hard times
regarding big/little endian. I'm on x86 working with build 77.
#zdb - ztest
...
rootbp = [L0 DMU objset] 400L/200P DVA[0]=0:e0c98e00:200
...
## zdb -R ztest:c0d1s4:e0c98e00:200:
Found vdev:
thanks for the quick reaction. I ve now a working binary for my system.
I don't understand why these changes should go through a project. The hooks
are already there so once the code is written no much work have to be done. But
it's an other story. Lets decode lzjb blocks now :-)
bbr
This
Hi Benjamin,
Benjamin Brumaire wrote:
I 'm trying to decode a lzjb compressed blocks and I have some hard times
regarding big/little endian. I'm on x86 working with build 77.
#zdb - ztest
...
rootbp = [L0 DMU objset] 400L/200P DVA[0]=0:e0c98e00:200
...
## zdb -R
Thanks Max, I have done a few tests with what you suggest and I have listed the
output below. I wait a few minutes before deciding it's failed, and there is
never any console output about anything failing, and nothing in any log files
I've looked in: /var/adm/messages or /var/log/syslog. Maybe
Hello Rustam,
Saturday, May 3, 2008, 9:16:41 AM, you wrote:
R I don't think that this is hardware issue, however i don't except this. I'll
try to explain why.
R 1. I've replaced all memory modules which are more likely to cause such a
problem.
R 2. There are many different applications
Well, I had some more ideas and ran some more tests:
1. cp -r testdir ~/z1
This copied the testdir directory from the zfs pool into my home directory on
the IDE boot drive, so not part of the zfs pool, and this worked.
2. cp -r ~/z1 .
This copied the files back from my home directory on the
The plot thickens. I replaced 'cp' with 'rsync' and it worked -- I ran it a few
times and it didn't hang so far.
So on the face of it, it appears that 'cp' is doing something that causes my
system to hang if the files are read from and written to the same pool, but
simply replacing 'cp' with
Hi Simon,
Simon Breden wrote:
The plot thickens. I replaced 'cp' with 'rsync' and it worked -- I ran it a
few times and it didn't hang so far.
So on the face of it, it appears that 'cp' is doing something that causes my
system to hang if the files are read from and written to the same pool,
oops, I lied... according to my self
http://mail.opensolaris.org/pipermail/zfs-discuss/2008-January/045141.html
wait are queued in solaris and active 1 are in
the drives NCQ.
so the question is: Where are the drive's command getting
dropped across 3 disks at the same time?
and in all cases
Thanks Max, and the fact that rsync stresses the system less would help explain
why rsync works, and cp hangs. The directory was around 11GB in size.
If Sun engineers are interested in this problem then I'm happy to run whatever
commands they give me -- after all, I have a pure goldmine here
Hi Simon,
Simon Breden wrote:
Thanks Max, and the fact that rsync stresses the system less would help
explain why rsync works, and cp hangs. The directory was around 11GB in size.
If Sun engineers are interested in this problem then I'm happy to run
whatever commands they give me -- after
I have similar, but not exactly the same drives:
format inq
Vendor: ATA
Product: WDC WD7500AYYS-0
Revision: 4G30
Same firmware revision. I have no problems with drive performance,
although I use them under UFS and for backing stores for iscsi disks.
FYI, I had random lockups and crashes on
Wow, thanks Dave. Looks like you've had this hell too :)
So, that makes me happy that the disks and pool are probably OK, but it does
seem an issue with the NVidia MCP 55 chipset, or at least perhaps the nv_sata
driver. From reading the bug list below, it seems the problem might be a more
15 matches
Mail list logo
