;/bin/mkdir -p /tmp/.diskless" fails.
>
> It should have been, but I went ahead and set tmpmfs="NO" in rc.conf,
> rebooted, and things are fine now.
>
> Thanks for the help!
Check if /tmp itself has strange permissions or file flags or
ownership
--
Bria
it still boots.
That's how it appears, yeah.
What does the drive health look like? Seems most like a chipset bug
or nvidia driver bug, but could be things are just coinciding with
drive or drive controller failure.
--
Brian Fundakowski Feldman \&
caveats. For
> example, AFAIK SCSI devices are under Giant and IDE are not - is there any
> reason this would make problems?
Might have bad performance, who knows. Why the funny setup exactly?
--
Brian Fundakowski Feldman \'[ FreeBSD
the em performance under 6.0-stable is half of any other box i have,
> and a similar mb running linux gives about 1GB, so
>
> Q: any ideas what can be wrong?
Performance of what? Do you even have a correct MTU set?
--
Brian Fundakowski Feldman \'[
>
> I should probably mention that this is with the drive formatted with
> a FAT filesystem.
Do you also know that nothing has /usb or a subdirectory of it open
as a current working directory, and that no files are open? You're
saying that the umount fails and t
On Thu, Dec 08, 2005 at 05:45:40PM -0600, Dan Nelson wrote:
> In the last episode (Dec 08), Brian Fundakowski Feldman said:
> > On Thu, Dec 08, 2005 at 05:29:06PM -, Steven Hartland wrote:
> > > It seems bsdtar can create files it cant read. i.e. it will happily create
> &
ean the tar itself inside of the gz.
{"/home/green" [EMAIL PROTECTED] tar cfv x.tar
tar: no files or directories specified
{"/home/green" [EMAIL PROTECTED] tar cfvz x.tar.gz
tar: no files or directories specified
{"/home/green" [EMAIL PROTECTED] ls -l x.t
Make sure you use 6.0-RELEASE or later so that you
have the fix for lock-ups in certain usage patterns and also configure
it for performance with "graid3 label -r".
--
Brian Fundakowski Feldman \'[ Fre
ua/dmesg.isc-cache
> kernel config - http://www.dp.uz.gov.ua/kernel.isc-cache
This is a samba server? It looks like you're using smbfs.
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
<> [EMAIL PR
On Mon, Dec 05, 2005 at 12:30:05PM +0100, kama wrote:
>
> The system crashed again this weekend, but nothing is created in
> /var/crash.
Try a serial console...
--
Brian Fundakowski Feldman \'[ FreeBSD ]'''&
t; I got a 32MB coredump but the same lack of understanding applies.
>
> Please tell me if I can be of any help! This is fun.
Do you have the ability to connect another computer by RS-232?
It's easy to get a serial terminal console going (err that is
if you find the right guide as opp
partition gets filled up, the build process failed and
> the computer continued to work as normal.
Yeah, it sounds like you're running into a buffer cache/VFS/VM deadlock.
They're nasty, but generally no
swap space is OK right before the
> freeze, but within 15 seconds from here, the kernel
> locks up
In my experience, fifteen seconds is enough to fill up 130+MB of swap,
so a much smaller polling interval is necessary.
--
Brian Fundakowski Feldman
r/src/sys/MYKERNEL.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
You may not have INVARIANT_SUPPORT -- I don't see that listed explicitly,
but it's necessary as well.
--
Brian Fundakowski Feldman \'[ Fr
f2200 in ?? () from /usr/local/lib/nss_ldap.so.1
Can you try making sure that nss_ldap gets built and linked with -g,
and is not stripped, so that all symbols and debug info are preserved
as well? Looks to be atexit(3)-related, from here, but the symbols
should clear thing
you have suggestion on what would be good text to go into pf.conf(5)
so that this particular case is documented?
--
Brian Fundakowski Feldman \'[ FreeBSD ]'''''''''
the crash every
> time.
Try running AbiWord using another computer as your X server, and
make the FreeBSD 6 machine stay at the console so it can potentially
hit DDB/KDB. A serial console is also helpful sometimes.
--
Brian Fundakowski Feldman \'[ FreeBSD ]'
/usr/local/lib
> SENDMAIL_LDADD=-lsasl
>
> Any clues on why this is failing with 6.0? It worked in 5.4 no
> problem...
You're still using your libsasl from 5.4. The warnings pretty
unequivocally showed that it can't find the libraries it was
orig
> 0 ]
> [ qlength: 0/ 50 borrows: 0 suspends: 0 ]
> [ measured: 199.0 packets/s, 146.71Kb/s ]
No it isn't, it's em0. You probably want to be using ALTQ on tun0.
I've done it; it works
--
Brian Fundakowski Feldman \'[ F
> No, you missed my point. I mean that kerberos libs are dynamic but
> > > linked against other libraries statically.
> >
> > If they were, there would be no problem in the first place.
>
> Sorry, it seems I missed a part of the thread.
Either the ports that use li
} --configure`.scan(/'([^'=]*)(?:=?([^']*))'/) {|lhs, rhs|
+ if lhs == "LDFLAGS"
+ pldflags = rhs
+ end
+}
+if pldflags
+ $LDFLAGS += " " + pldflags
+ puts "Using PostgreSQL build flags: #{pldflags}"
+
On Thu, Jun 30, 2005 at 03:53:56PM +0200, Eirik Øverby wrote:
>
> On 29. jun. 2005, at 20.58, Brian Fundakowski Feldman wrote:
>
> >On Wed, Jun 29, 2005 at 03:28:09PM +0200, Eirik Øverby wrote:
> >
> >>
> >>On 28. jun. 2005, at 16.58, Brian Fundakowski Fe
gt; >@400042c1badc250a9cd4 status: local 0/30 remote 0/20
> >@400042c1badc250c7d4c end msg 24087
> >@400042c1badc2510942c end msg 24040
The filesystem looks the same before, during, and after
On Wed, Jun 29, 2005 at 03:28:09PM +0200, Eirik Øverby wrote:
>
> On 28. jun. 2005, at 16.58, Brian Fundakowski Feldman wrote:
>
> >On Tue, Jun 28, 2005 at 10:37:29AM +0200, Eirik Øverby wrote:
> >
> >>Hi,
> >>
> >>I have, since upgrading to
pertaining to the jail, though it has no processes running. I
> have therefore force-started the jail again, which seems to work
> nicely, but now 'jls' gives me two entries for this jail, with
> different JIDs.
>
> What am I doing wrong here?
You could just use ps to
ause I'm not sure the problem is recognized.
>
> I have two separate Intel IHC5 based boxes affected by DMA TIMEOUTS,
> both with SATA drives and I'd like to get to the bottom of this.
The best thing to do is narrow down what kernel changes caused this
(build kerne
elf without even updating libc or the kernel.
No guarantees, but it's something I've always found to work alright.
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
<> [EMAIL PROTECTED
never tried the IPFW-compatible bridge(4) before,
but it is significantly broken (crashes bridging two fxp(4)). So
caveat emptor using it as a firewall for the time being... The other
problem I have had is that doing CD burning can sometimes crash the
system, but I haven&#
On Tue, May 03, 2005 at 11:47:00AM +0200, Marc Olzheim wrote:
> On Wed, Apr 27, 2005 at 12:08:57PM -0400, Brian Fundakowski Feldman wrote:
> > Alright, this will do synchronous, instead of short, writes (also,
> > of course, not deadlock the system) if you are trying to use an
On Wed, Apr 27, 2005 at 09:19:38PM +0200, Marc Olzheim wrote:
> On Wed, Apr 27, 2005 at 03:06:27PM -0400, Brian Fundakowski Feldman wrote:
> > > How can I tell whether it uses transactions ?
> >
> > I am not sure -- it should with NFSv3 though. Does "mount -v" t
On Wed, Apr 27, 2005 at 08:42:03PM +0200, Marc Olzheim wrote:
> On Wed, Apr 27, 2005 at 02:34:35PM -0400, Brian Fundakowski Feldman wrote:
> > Alright, thanks for helping with this :-) Do you think you can find
> > a way to tell if in 4.x you're actually using NFSv3/transa
On Wed, Apr 27, 2005 at 07:15:23PM +0200, Marc Olzheim wrote:
> On Wed, Apr 27, 2005 at 12:08:57PM -0400, Brian Fundakowski Feldman wrote:
> > > Yes, a single writev(). Just like in the kern/79207 PR.
> > >
> > > It doesn't have to be superfast (why would I use
On Wed, Apr 27, 2005 at 10:17:46AM +0200, Marc Olzheim wrote:
> On Tue, Apr 26, 2005 at 03:36:02PM -0400, Brian Fundakowski Feldman wrote:
> > I'm still guessing that for whatever reason your writes on the FreeBSD
> > 4.x NFS client are not using NFSv3/transactions. The seco
On Tue, Apr 26, 2005 at 06:43:46PM +0200, Marc Olzheim wrote:
> [changed cc: from standards@ back to stable@ again.]
>
> On Tue, Apr 26, 2005 at 12:25:49PM -0400, Brian Fundakowski Feldman wrote:
> > You can assure that this happens in only two ways:
> >
> > 1. Make
ries. Some stuff sometimes pops up in lost+found. Some
> stuff can vanish (not 100% positive on that). But most worringly, is
> that some files come back corrupted (ie berkley db files that db won't
> read).
Long strings of NUL bytes? Missing data? Spam (from the same file,
or from
;m going to
test all major bugfixes for a lot longer to make certain there aren't
problems that are easy to miss (triggering).
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[EMAIL PROTECTED]`--'
To Uns
g in
the kernel memory, like pidentd, would need to be recompiled/modified,
but pidentd itself (now uses the proper interface to get the data it needs.
So, anyone who can, test it out and report back. I need to get this
done within the week or so :)
--
Brian Fundakowski Feldman \ Fre
37 matches
Mail list logo
