Yes, I believe so.
On Thu, Feb 24, 2022 at 7:42 AM Larry Rosenman wrote:
> On 02/24/2022 10:36 am, Rob Wing wrote:
>
> You might try setting `sysctl vfs.zfs.recover=1` and `sysctl
> vfs.zfs.spa.load_verify_metadata=0`.
>
> I had a similar error the other day (couple months ag
You might try setting `sysctl vfs.zfs.recover=1` and `sysctl
vfs.zfs.spa.load_verify_metadata=0`.
I had a similar error the other day (couple months ago). The best I did was
being able to import the pool read only. I ended up restoring from backup.
On Thu, Feb 24, 2022 at 7:30 AM Alexander Motin
Hey Mike,
Should be fixed in commit 0a2f498234023008d9a3b13ad7fc8fd81d384bab
<https://cgit.freebsd.org/src/commit/?id=0a2f498234023008d9a3b13ad7fc8fd81d384bab>
Thanks for the report
-Rob
On Mon, Feb 21, 2022 at 7:48 PM Rob Wing wrote:
> Think that's it...thanks for testing
Think that's it...thanks for testing for the patch.
I opened up https://reviews.freebsd.org/D34335 for review.
-Rob
On Mon, Feb 21, 2022 at 6:05 PM Michael Jung
wrote:
> Rob:
>
>
>
> I did not remove Hans earlier patch, but your “latest” patch applied and
> compiled wi
The previous attached patch should work for testing purposes, but it's
incorrect if an error occurs.
The fhold() should be below FILEDESC_SUNLOCK(), this patch addresses that.
On Mon, Feb 21, 2022 at 5:18 PM Rob Wing wrote:
> try the attached patch
>
> On Mon, Feb 21, 2022 at 5
try the attached patch
On Mon, Feb 21, 2022 at 5:14 PM Michael Jung
wrote:
>
>
>
>
>
> CONFIDENTIALITY NOTE: This message is intended only for the use
> of the individual or entity to whom it is addressed and may
> contain information that is privileged, confidential, and
> exempt from disclosur
kinda thinking this might be related to commit f40dd6c8034b ("tty: switch
ttyhook_register to use fget_cap_locked")
fget_unlocked() must have grabbed an extra reference count on the file
pointer that fget_cap_locked() doesn't get
On Mon, Feb 21, 2022 at 4:35 PM Hans Petter Selasky wrote:
> On 2
> Hi,
>
> I recently noticed that if I do a 'shutdown -p' from -CURRENT, the
> system would shut down and seemingly powered off, then it would restart
> after about 5-10 seconds.
>
> Is this a known issue? Arguably this is not necessarily a FreeBSD
> issue, but it seems that the Windows 10 install
On Sun, Jan 23, 2011 at 21:13, Warren Block wrote:
> On Sun, 23 Jan 2011, Rob Farmer wrote:
>
>> On Sun, Jan 23, 2011 at 07:32, LOL wrote:
>>>
>>> Hi guys.
>>> On every release of freebsd that i tried (-CURRENT, -STABLE, -RELEASE)
>>> everything
s xf86-video-radeonhd. And
try the WITHOUT_NOUVEAU knob as David suggests.
ports or x11 are better lists for this - current is for things in the
base system.
--
Rob Farmer
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebs
fusing, because many common
(non-compliant) date systems use hyphens or slashes with the
components in different orders. Omitting it is non-intuitive to
everyone and thus least likely to cause confusion due to local
assumptions in cases like 2001-01-02.
--
Rob Farmer
___
team on Linux, which Value has consistently said isn't
happening).
--
Rob Farmer
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
and I'm definitely not a great
programmer). So the fact that it wasn't fixed either means nobody
cares about that port (somewhat true here - most of the KDE people
moved on to 4) or that the fix will be more involved (probably the
case for this one
On Mon, Nov 1, 2010 at 23:14, Matthias Apitz wrote:
> Something wrong with 'struct utmp ubuf' in HEAD?
It has been removed:
http://lists.freebsd.org/pipermail/freebsd-current/2010-January/014893.html
--
Rob Farmer
___
freebsd-curren
es (of course, that can
add up) or starts to cut into basic functionality (like no man pages),
IMHO.
--
Rob Farmer
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail t
- root is still
mounted read only in single user, as before.
--
Rob Farmer
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
rrent.
Some necessary support was removed recently, but it has be re-added.
See r213739.
--
Rob Farmer
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd
problem enough.
The system is a HP Pavillion dv6405us laptop with a GeForce Go 6150.
This is a pretty crappy card, even in Windows (the whole system was
$500 3 years ago - it was one of those computers that supposedly was
"Vista Ready" but could barely boot it
solves the problem. Using sendfile with
a UFS partition on the same machine causes no problems.
--
Rob Farmer
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "
you would recommend for
general ZFS use on current? (I assume it only matters when WITNESS is
enabled)
--
Rob Farmer
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
On Thu, Sep 9, 2010 at 15:14, Xin LI wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi, Rob,
>
> On 2010/09/09 15:01, Rob Farmer wrote:
> [...]
>>> Just a guess - are you compiling under X? If so what about if you
>>> compile under text m
On Thu, Sep 9, 2010 at 14:56, Xin LI wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 2010/09/09 14:51, Rob Farmer wrote:
>> I am running a fairly recent current with the new ZFS patches:
>>
>> FreeBSD topaz.predatorlabs.net 9.0-CURRENT FreeBSD 9.0-C
up to date:
# $FreeBSD: ports/databases/mysql51-client/Makefile,v 1.100 2010/08/25
09:07:27 ale Exp $
Not sure if this is ZFS related or not. What can I do to collect some
useful information here? This can be reproduced reliably.
Thanks,
--
Rob F
been around 50 "ERROR: unable to cvsup the
source tree" mails in the last week.
--
Rob Farmer
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Sun, Sep 5, 2010 at 10:15, wrote:
>
> Rob,
>
> IMO the question is not if the problem _can_ be solved in the base build
> system. I doubt you'll find many src committers willing to break other
> peoples machines by using DISABLE_CONFLICTS as a general problem solver.
&
On Thu, Sep 2, 2010 at 23:57, jhell wrote:
> On 09/02/2010 04:55, Rob Farmer wrote:
>>
>> I tried applying the patch to r212087 to rule out recent changes to
>> dtrace, but it made no difference. I used patch -E -p0 < patch.
>>
>
> Hi Rob,
>
> I see that
ied applying the patch to r212087 to rule out recent changes to
dtrace, but it made no difference. I used patch -E -p0 < patch.
--
Rob Farmer
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
_tsc=1 works for me. I put it in
/boot/loader.conf so it would automatically work for single user mode
too. I don't think the host automatically synchronizes the clock -
their website recommends running ntp and I saw the clock drift a fair
amount before I started doing that.
Thanks for the ti
On Thu, Jul 15, 2010 at 11:33 PM, Alexander Motin wrote:
> Rob Farmer wrote:
>> I have a VPS from rootbsd.net which is running current, though I don't
>> update it very often. I just built and installed a new world and
>> kernel and now the clock will not move fr
msec
ad0: 10240MB at ata0-master WDMA2
SMP: AP CPU #1 Launched!
Thanks,
--
Rob Farmer
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Sun, May 23, 2010 at 11:02 PM, James R. Van Artsdalen
wrote:
> On 5/22/2010 8:25 PM, Rob Farmer wrote:
>> make release is still broken on amd64 as of svn 208373 (2010-05-21
>>> 04:52:49 -0500)
>>>
>>> That patch seems unrelated?
>>>
>> What n
On Sat, May 22, 2010 at 8:09 AM, James R. Van Artsdalen
wrote:
> On 5/18/2010 2:34 AM, jhell wrote:
>> On Mon, May 17, 2010 at 10:35 PM, Rob Farmer
>> wrote:
>>>> make release is broken on current. Seems to be related to the lzma
>>>> import. This is on i3
ion `xz_filter_read':
: undefined reference to `lzma_code'
*** Error code 1
Stop in /usr/obj/usr/src/release/boot_crunch.
*** Error code 1
Stop in /usr/src/release.
+ umount /dev
*** Error code 1
Stop in /usr/src/release.
--
Rob Farmer
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
te unzipped
configure scripts, for example)
* different semantics of CR/LF conversion
Error logs of failed port builds with in-base unzip can be made available on
request to port...@.
With hat: portmgr
--
Rob Farmer
>>
>> .if defined(USE_ZIP) && !exists(/usr/b
On Wed, Mar 10, 2010 at 8:43 AM, Rob Farmer wrote:
> Hi,
>
> I just updated a sparc64 Sun Netra X1 running current. I am using PF
> (built into the kernel) and now I cannot connect to the machine while
> PF is enabled (but outbound traffic from the machine works). The same
>
() at intr_event_execute_handlers+0xc4
ithread_loop() at ithread_loop+0xe4
fork_exit() at fork_exit+0x6c
fork_trampoline() at fork_trampoline+0x8
My pf.conf:
http://www.predatorlabs.net/dl/pf.conf
My kernel config:
http://www.predatorlabs.net/dl/NETRA
Thanks,
--
Rob F
r/src.
ekg#
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Cvsup again,
It shou
27;s a privacy issue.
Reply-to mangled to assist those who don't read the above.
--
Rob | What part of "no" was it you didn't understand?
_
Hotmail messages di
12:38:03 - 1.8
+++ ata-queue.c 13 Oct 2003 13:05:01 -
<---SNIP--->
Happy to say that this patch fixes the "resetting devices..." problem I'd
encountered.
Thanks.
--
Rob | What part of "
From: "Rob MacGregor" <[EMAIL PROTECTED]>
Same result for me as with 1.7. I've just grabbed 1.6 and am rebuilding to
confirm that that's the last working version for me too.
Backing out to 1.6 fixes the problem for me too...
Please DO NOT send me ANY email directly u
a privacy issue.
Reply-to mangled to assist those who don't read the above.
--
Rob | What part of "no" was it you didn't understand?
_
Get Hotmail on your mobile phone http://www.msn.co.uk/msnmobile
___
NT before I'm a
little out of my depth :)
--
Rob | What part of "no" was it you didn't understand?
_
Stay in touch with absent friends - get MSN Messenger
http://www.msn.co.uk/messenger
___
.
Anyone with the same problems and/or ideas ?
Rob Evers
--
It is a book about a Spanish guy called Manual. You should read it.
-- Dilbert
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe,
Greg 'groggy' Lehey wrote:
On Tuesday, 5 August 2003 at 22:21:41 +0200, Rob wrote:
Poul-Henning Kamp wrote:
In message <[EMAIL PROTECTED]>, Rob writes:
Hi all,
After cvs'upping (about 12 hours ago) and building world/kernel vinum
stopped working. It does show my two disk
Poul-Henning Kamp wrote:
In message <[EMAIL PROTECTED]>, Rob writes:
Hi all,
After cvs'upping (about 12 hours ago) and building world/kernel vinum
stopped working. It does show my two disks but nothing more. I also
get an error message right after the bootloader:
Can you try
Simon L. Nielsen wrote:
On 2003.06.25 18:38:59 +0200, Rob wrote:
I get e-mails from my current boxes saying: "hostname: sethostname:
Operation not permitted" (original message attached).
I know this is the random seed saving instance of crontab, but what
goes wrong here ? (why do
Hi all,
I get e-mails from my current boxes saying: "hostname: sethostname:
Operation not permitted" (original message attached).
I know this is the random seed saving instance of crontab, but what
goes wrong here ? (why does it fail permission)
The box is updated today and mergemaster was run (T
/usr/src/sys/AYLEE alpha
cheers,
Rob
--
When in doubt, fuck it. When not in doubt ... get in doubt!
This is random quote 1185 of 1254.
Distance from the centre of the brewing universe
[15200.8 km (8207.8 mi), 262.8 deg](Apparent) Rennerian
Public Key fingerprint = 6219 33BD A37B 368D 29F5
At 11:59 AM 31/03/03, Glenn Johnson sent this up the stick:
On Mon, Mar 31, 2003 at 10:46:07AM +1000, Rob B wrote:
> At 02:55 PM 29/03/03, Terry Lambert sent this up the stick:
> >
> >man ypbind
> >
> >(-s is the magic incantation).
>
> Mar 31 10:
cally
told it to bind to a low port?
Cheers,
Rob
--
On Earth there is no reckoning.
This is random quote 883 of 1254.
Distance from the centre of the brewing universe
[15200.8 km (8207.8 mi), 262.8 deg](Apparent) Rennerian
Public Key fingerprint = 6219 33BD A37B 368D 29F
Mar 27 09:46:04 aylee sshd[23711]: fatal: login_get_lastlog: cannot find
account for uid[1000]
cheers,
Rob
--
A beautiful woman will enrich your life soon.
This is random quote 120 of 1254.
Distance from the centre of the brewing universe
[15200.8 km (8207.8 mi), 262.8 deg](Apparent) Renne
tes)
/dev/da0g on /var (ufs, local, soft-updates)
Also:
1) I'm sure I'm mounting as root.
2) As you can see both machines know the route for the other.
Does the client have the following in /etc/rc.conf ?
nfs_client_enable="YES"
nfs_client_flags="-n 4"
rpc_lock
DS UP: VFS changes breaks GPT
Rob
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I've seen a few discussions of sysinstall vs disklabels, but this
problem looks a little different.
I sliced up a 37G disk with 4.7-RELEASE on ad0s1, Win2k on ad0s[23]
and ad0s4 empty. I installed grub-0.92, putting the bootloader in
the MBR and config files in ad0s1a. Everything worked fine.
The
than
-current. Some mobo's just don't work. If I knew all the answers I'd
write a HOWTO.
Rob.
--
-
The Numeric Python EM Project
www.pythonemproject.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
;
> Load"extmod"
> Load"glx"
> Load"pex5"
> Load"record"
> Load"xie"
> Load"bitmap"
> Load"freetype"
> Load"
h worse than earlier
builds. I did once get the nv.tar.gz method working on my laptop. That
was from a cvsup the day after DP2 came out.
Good grief, I couldn't even get grub to load so I could try out OpenBSD
on drive #2. Time to do something else instead of computers.
Rob.
--
-
>
> Ok, here is the error message. The server never even gets past go:
>
> "Symbol vgaHWUnmapMem from module
> /usr/X11R6/lib/modules/drivers/nv_drv.o is unresolved!"
> Fatal server error:
> Caught signal 11. Server aborting.
>
> Rob.
>
> --
I go
Joe Marcus Clarke wrote:
>
> On Wed, 2002-12-04 at 22:46, Rob wrote:
> > Rob wrote:
> > >
> > > Joe Marcus Clarke wrote:
> > > >
> > > > On Wed, 2002-12-04 at 17:04, Rob wrote:
> > > > > Is there any solution to the above comb
Rob wrote:
>
> Joe Marcus Clarke wrote:
> >
> > On Wed, 2002-12-04 at 17:04, Rob wrote:
> > > Is there any solution to the above combo other than just waiting?
> >
> > I think you've seen my how-to at
> > http://www.marcuscom.com/g2g-xfree86/ar
Joe Marcus Clarke wrote:
>
> On Wed, 2002-12-04 at 17:04, Rob wrote:
> > Is there any solution to the above combo other than just waiting?
>
> I think you've seen my how-to at
> http://www.marcuscom.com/g2g-xfree86/article.html. Did it not work for
> your card, or a
Is there any solution to the above combo other than just waiting?
thanks, Rob.
--
-
The Numeric Python EM Project
www.pythonemproject.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hi Garance,
This happened to me also. The solution was to run fsck on the older
versions, but tell it to use an alternate superblock. See man fsck. I
forget the details, but it worked for me.
Rob.
Garance A Drosihn wrote:
>
> I'm playing around with installing a number of freeb
John Baldwin wrote:
>
> On 22-Nov-2002 Rob wrote:
> > Can DP2 be cvsup'd?
>
> Not directly, no. It was not done as a branch in CVS. However,
> the differences between CVS and DP2 are relatively minor, mostly
> just going around and change it to say 5.0
Can DP2 be cvsup'd?
Thanks, Rob.
--
-
The Numeric Python EM Project
www.pythonemproject.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hi all,
I agree keeping these traditional toys in the base system won't help in a better
OS (instead it makes it a bit bigger and older), agreed that they are some sort
of 'folklore' putting them in a port makes a good solution.
mzl! Rob Evers
[EMAIL PROTECTED]
Technologic
TED]
> with "unsubscribe freebsd-current" in the body of the message
I will wait for a while for things to be cleaned up, but what tags would
I use for CVSUP to get that branch?
Thanks, Rob.
--
-
The Numeric Python EM Project
www.pythonemproject.com
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sat, 2002-08-03 at 00:45, karl agee wrote:
> ok...its crashing here, now.I've deleted the /usr/src/gnu directory
> and re-cvsuped it, but it still_crashes:
>
>
Re-cvsup and try it again. I got that Thursday, but Friday it worked.
Well, the system locked at loading the fxp driver, but it
I cvsup'd on Friday of last week, after I restored /usr. Did the fix come later than
that? I'm kind of afraid to try it again :) Thanks, Rob.
>- Original Message -
>From: Dag-Erling Smorgrav <[EMAIL PROTECTED]>
>To: rob <[EMAIL PROTECTED]>
>
on it freezes and you have to take the
batteries out to get it working right again.
Rob. (ps. this is the message I was trying to send that ended up as
dozens of "QUIT" messages- sorry again)
--
-
The Numeric Python EM Project
www.pythonemproject.com
To Un
gt; -Maxim
BTW, the VESA mode doesn't work on -stable now either. I knew I
shouldn't have cvsup'd, with all the problem reports I'm seeing on the
lists. Dohh! But I just ordered a Dell 8200, so maybe my problems will
become "different" Rob.
To Unsubscribe: send ma
This is either a problem with linux-netscape on -current, or a problem
with the mta at Verio (on FBSD of course).
Sorry for the inconvenience. I hope it isn't at Verio, or there will be
another 30 messages. Rob.
--
-
The Numeric Python EM Pr
There was either a glitch at Verio's mta or possibly on Linux-Netscape in -current. I
sent one message and it never went through. Sorry for the spam. It was an error
message- get it?
Rob.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
1 - 100 of 130 matches
Mail list logo
