On Thu, 28 Oct 2004, Dan Strick wrote:
DSOn Thu, 28 Oct 2004 03:23:02 -0700, I wrote:
DS
DS I just spent a *very* frustrating hour trying to figure out why the
DS FreeBSD make program was invoking all commands to make things in a
DS subdirectory named obj. I eventually discovered this gem in the
On Thu, 28 Oct 2004, Sean Farley wrote:
SFOn Thu, 28 Oct 2004, Dan Strick wrote:
SF
SF On Thu, 28 Oct 2004 03:23:02 -0700, Dan Strick wrote:
SF
SF I just spent a *very* frustrating hour trying to figure out why the
SF FreeBSD make program was invoking all commands to make things in a
SF
The box has been quite unstable, with restarts every few days
this is the first dump ive got with DDB
I realize this likely isnt enough information, but if you could point me in the right
direction
I can provide anymore information required.
uname -a
FreeBSD *** 4.8-STABLE
On 8th October, Mikhail P. [EMAIL PROTECTED] reported the error:
ad0: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=10NID_NOT_FOUND
LBA=268435455
On Sun, 10 Oct 2004, Søren Schmidt wrote:
so that leaves the disks for scrutiny. One thing to try is change the
tripping point where we
On Thu, 28 Oct 2004 21:30:45 -0300, Allan Marshall [EMAIL PROTECTED] wrote:
The box has been quite unstable, with restarts every few days
this is the first dump ive got with DDB
I realize this likely isnt enough information, but if you could point me in the
right direction
I can provide
Are there any whitepapers, documentation, etc (aside from the new book
about 5.2) on GEOM? I've been reading over the code and it would be nice
to have an annotation to go with it.
--
Ryan Sommers
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
Ryan Sommers [EMAIL PROTECTED] writes:
Are there any whitepapers, documentation, etc (aside from the new book
about 5.2) on GEOM? I've been reading over the code and it would be nice
to have an annotation to go with it.
http://www.google.com/search?q=phk+geom+paper
DES
--
Dag-Erling Smørgrav
This sounds very possible to me. I have been experiencing the same
error, on a system that I've been trying to set up using 5.3-RC1 and
a new 160Gbyte SATA drives My hardware is:
atapci0: SiI 3112 SATA150 controller port
0xb000-0xb00f,0xac00-0xac03,0xa800-0xa807,0xa400-0xa403,0xa000-0xa007
Hi,
I am writing this pseudo disk driver for disk checkpointing, which
intercepts write requests to the disk (ad0s1) and performs a copy on write
of the old contents to another partition (ad0s4) before writing out the
new contents. So the driver (called shd) is mounted as
/dev/shd0a on /
On Friday 29 October 2004 16:44, [EMAIL PROTECTED] wrote:
The same problem with similar IDE Seagate HDD:
ad0: ST3160023A/3.06 ATA-6 disk at ata0-master
ad0: 152627MB (312581808 sectors), 310101 C, 16 H, 63 S, 512 B
[...]
ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=10NID_NOT_FOUND
On Friday 29 October 2004 16:50, Mikhail P. wrote:
Perhaps it is only Seagate - FreeBSD5-related. Same drives, but with
FreeBSD4 do work well together without a glitch.
Actually not only seagates.. similar happened on a 200GB Western Digital drive
to me, FreeBSD-5.3.
regards,
M.
Another related question ...
Is it possible to delay or queue up disk writes until I exit from my
function in the kernel (where I am trying to sync with the disk)? Or
make sure that my sync function never goes to sleep waiting for the disk
driver to signal completion of flushes to disk?
On Fri,
On 29 Oct, Siddharth Aggarwal wrote:
Another related question ...
Is it possible to delay or queue up disk writes until I exit from my
function in the kernel (where I am trying to sync with the disk)? Or
make sure that my sync function never goes to sleep waiting for the disk
driver to
Thanks for your reply.
Hmm. At the moment, the user can send an ioctl to define a checkpoint. But
I would guess that this could happen between 2 strategy() function calls
corresponding to the same filesystem operation? So if there a way to block
filesystem operations while a snapshot is taken? I
On Fri, 29 Oct 2004, Mikhail P. wrote:
On Friday 29 October 2004 16:50, Mikhail P. wrote:
Perhaps it is only Seagate - FreeBSD5-related. Same drives, but with
FreeBSD4 do work well together without a glitch.
Actually not only seagates.. similar happened on a 200GB Western Digital drive
to
Add Western Digital Raptors to the list as well. However I have not
had a problem since 5.3-BETA3.
aaron.glenn
On Fri, 29 Oct 2004 16:57:33 +, Mikhail P. [EMAIL PROTECTED] wrote:
On Friday 29 October 2004 16:50, Mikhail P. wrote:
Perhaps it is only Seagate - FreeBSD5-related. Same drives,
Why are you unable to do anything with the command-line? Any of these
will solve your problem.
Bourne:
MAKEOBJDIR=/no_obj_here make
Bourne or CSH:
env MAKEOBJDIR=/no_obj_here make
Here is a Makefile that does not use obj/. The special targets can be
placed into a file to be included
Hi
First of all, I know that most committers or contributors contribute
their work in their free time.
I am not asking for any promise but I just want to discuss a possible
improvement for FreeBSD.
So my suggestion is: integrate pam_ldap, nss_ldap, nsswitch support
with ldap and lookupd (ie LDAP
18 matches
Mail list logo
