adding vnet macros),
> > >>>>>>>>> but it also includes export check changes.
> > >>>>>>>>>
> > >>>>>>>>> I have attached a trivial patch that I think disables the export
> > >>>
arge # of changes (mostly trivial edits adding vnet macros),
> >>>>>>>>> but it also includes export check changes.
> >>>>>>>>>
> >>>>>>>>> I have attached a trivial patch that I think disables the export
&g
t;>>>>
>>>>>>>>> I have attached a trivial patch that I think disables the export
>>>>>>>>> checks for jails. If either of you can try it and see if it fixes
>>>>>>>>> the problem, that would be great.
>>&g
>>>> a large # of changes (mostly trivial edits adding vnet macros),
> >>>>>>> but it also includes export check changes.
> >>>>>>>
> >>>>>>> I have attached a trivial patch that I think disables the export
&g
;>>>>>>
>>>>>>> I have attached a trivial patch that I think disables the export
>>>>>>> checks for jails. If either of you can try it and see if it fixes
>>>>>>> the problem, that would be great.
>>>>>>
the export
> >>>>> checks for jails. If either of you can try it and see if it fixes
> >>>>> the problem, that would be great.
> >>>>> (Note that this is only for testing, although it probably does not
> >>>>> matter unless yo
lso includes export check changes.
> >>>>
> >>>> I have attached a trivial patch that I think disables the export
> >>>> checks for jails. If either of you can try it and see if it fixes
> >>>> the problem, that would be great.
> &
;>
> > >> I have attached a trivial patch that I think disables the export
> > >> checks for jails. If either of you can try it and see if it fixes
> > >> the problem, that would be great.
> > >> (Note that this is only for testing, although it
(Note that this is only for testing, although it probably does not
matter unless you are running nfsd(8) in vnet jails.)
Yes, I can see snapshots with the patch. This system is just a test
system that doesn't normally run ZFS or NFS, so no problem messing
with permissions. It's a
s: "man zfs-snapshot" for "zfs snapshot" commands.
I mention this in part because it references also using "zfs promote"
to swap around the status of what is a snapshot vs. what is not.
There is also the man page, accessible via: "man zfs-promote" .
man zfs-
r jails. If either of you can try it and see if it fixes
> >> the problem, that would be great.
> >> (Note that this is only for testing, although it probably does not
> >> matter unless you are running nfsd(8) in vnet jails.)
> >
> > Yes, I can see snapshots wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
New FreeBSD development branch installation ISOs and virtual machine
disk images have been uploaded to the FreeBSD Project mirrors.
As with any development branch, the installation snapshots are not
intended for use on production systems. We do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
New FreeBSD development branch installation ISOs and virtual machine
disk images have been uploaded to the FreeBSD Project mirrors.
As with any development branch, the installation snapshots are not
intended for use on production systems. We do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
New FreeBSD development branch installation ISOs and virtual machine
disk images have been uploaded to the FreeBSD Project mirrors.
As with any development branch, the installation snapshots are not
intended for use on production systems. We do
Ship it!
Glen
Sent from my phone.
Please excuse my brevity and/or typos.
> On Aug 13, 2023, at 2:39 PM, George Mitchell wrote:
>
> On 8/11/23 23:15, Glen Barber wrote:
>> [...]
>> It was discovered that due to human error (my own) the arm64 are, as
>> Colin put it very politely, are "lacking '
On Fri, Aug 11, 2023 at 08:53:12PM +, Glen Barber wrote:
[...]
> FreeBSD/aarch64 UFS EC2 AMIs are available in the following regions:
>
[...]
>
> FreeBSD/aarch64 ZFS EC2 AMIs are available in the following regions:
>
[...]
It was discovered that due to human error (my own) the arm64 are,
New FreeBSD development branch installation ISOs and virtual machine
disk images have been uploaded to the FreeBSD Project mirrors.
As with any development branch, the installation snapshots are not
intended for use on production systems. We do, however, encourage
testing on non-production
On Tue, 16 Nov 2021 at 23:22, Li-Wen Hsu wrote:
>
> You can use this command to list all the images built by re:
>
> gcloud compute images list --no-standard-images
> --project=freebsd-org-cloud-dev
Aside, it looks like we have many EOL images that are not marked as
deprecated in the gcloud l
Thanks! That's just what I was looking for.
On Tue, Nov 16, 2021 at 9:20 PM Li-Wen Hsu wrote:
>
> On Wed, Nov 17, 2021 at 11:56 AM Alan Somers wrote:
> >
> > Google Compute Engine has images for 11.4-RELEASE, 12.2-RELEASE, and
> > 13.0-RELEASE. Are there any imag
On Wed, Nov 17, 2021 at 11:56 AM Alan Somers wrote:
>
> Google Compute Engine has images for 11.4-RELEASE, 12.2-RELEASE, and
> 13.0-RELEASE. Are there any images for current snapshots, and if so
> what are their names?
> -Alan
You can use this command to list all the ima
Google Compute Engine has images for 11.4-RELEASE, 12.2-RELEASE, and
13.0-RELEASE. Are there any images for current snapshots, and if so
what are their names?
-Alan
On Fri, 25 Sep 2020 21:13:28 +0300
xto...@hotmail.com wrote:
> Sergey V. Dyatko wrote:
> > Hi,
> >
> > Possible I missed the answer to my question, sorry. But
> > Today I installed FreeBSD from
> > FreeBSD-13.0-CURRENT-amd64-20200924-3c514403bef-disc1
> > and now I want to rebuild kernel and so
Sergey V. Dyatko wrote:
Hi,
Possible I missed the answer to my question, sorry. But
Today I installed FreeBSD from
FreeBSD-13.0-CURRENT-amd64-20200924-3c514403bef-disc1
and now I want to rebuild kernel and so on BUT I don't know which SVN revision
should I checkout.
uname -a output:
FreeBSD my.
Hi,
Possible I missed the answer to my question, sorry. But
Today I installed FreeBSD from
FreeBSD-13.0-CURRENT-amd64-20200924-3c514403bef-disc1
and now I want to rebuild kernel and so on BUT I don't know which SVN revision
should I checkout.
uname -a output:
FreeBSD my.host.name 13.0-CURRENT Fre
On Thu, Sep 10, 2020 at 04:53:30PM +, Glen Barber wrote:
> On Thu, Sep 10, 2020 at 06:43:08PM +0200, Emmanuel Vadot wrote:
> > Which port commit and which board ? There haven't been a commit in the
> > u-boot ports or rpi-firmware this a month now so I fails to understand
> > without more info
clay@bsd13:~ $ uname -a
FreeBSD bsd13 13.0-CURRENT FreeBSD 13.0-CURRENT #0
1544934ffb2-c253004(main): Thu Sep 10 06:18:34 UTC 2020
r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
Works great, no problems with snapshot, thanks much Glen & everybody.
> > >
> > > > > > -BEGIN PGP SIGNED MESSAGE-
> > > > > > Hash: SHA256
> > > > > >
> > > > > > New FreeBSD development branch installation ISOs and virtual machine
> > > > > > disk images have be
gt;
> > > > > New FreeBSD development branch installation ISOs and virtual machine
> > > > > disk images have been uploaded to the FreeBSD Project mirrors.
> > > > >
> > > > > NOTE: These are the first snapshots built from the FreeBSD Git
>
3 Sep 2020 15:02:45 +
> > > Glen Barber wrote:
> > >
> > > > -BEGIN PGP SIGNED MESSAGE-
> > > > Hash: SHA256
> > > >
> > > > New FreeBSD development branch installation ISOs and virtual machine
> > > > disk images h
> > > Hash: SHA256
> > >
> > > New FreeBSD development branch installation ISOs and virtual machine
> > > disk images have been uploaded to the FreeBSD Project mirrors.
> > >
> > > NOTE: These are the first snapshots built fr
s and virtual machine
> > disk images have been uploaded to the FreeBSD Project mirrors.
> >
> > NOTE: These are the first snapshots built from the FreeBSD Git sources.
> > Also note: The armv6 and armv7 builds failed, and the cause is being
> > investigated.
>
>
the following architectures:
o 13.0-CURRENT amd64
o 13.0-CURRENT i386
o 13.0-CURRENT aarch64
Disk images may be downloaded from the following URL (or any of the
FreeBSD Project mirrors):
https://download.freebsd.org/ftp/snapshots/VM-IMAGES/
Images are available in the following disk image
Hello,
On Thu, 3 Sep 2020 15:02:45 +
Glen Barber wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> New FreeBSD development branch installation ISOs and virtual machine
> disk images have been uploaded to the FreeBSD Project mirrors.
>
> NOTE: These ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
New FreeBSD development branch installation ISOs and virtual machine
disk images have been uploaded to the FreeBSD Project mirrors.
NOTE: These are the first snapshots built from the FreeBSD Git sources.
Also note: The armv6 and armv7 builds failed
On 28/03/2020 15:19, Allan Jude wrote:
> You can try to destroy the snapshot, if it is the basis of a clone, then
> you will get an error, that you'd need to destroy the BE first, so you
> might decide to keep that snapshot. As long as you don't use the -R flag
> to zfs destroy dataset@snapshot,
On 2020-03-28 03:24, Graham Perrin wrote:
> I imagine that some of the 2019 snapshots below are redundant.
>
> Can I safely destroy any of them?
>
> $ zfs list -t snapshot
> NAME USED AVAIL
> REFER MOUNTPOINT
> coppe
On Sat, Mar 28, 2020 at 10:30 AM Graham Perrin wrote:
>
> I imagine that some of the 2019 snapshots below are redundant.
>
> Can I safely destroy any of them?
>
> $ zfs list -t snapshot
> NAME USED AVAIL
> REFER MOUN
I imagine that some of the 2019 snapshots below are redundant.
Can I safely destroy any of them?
$ zfs list -t snapshot
NAME USED AVAIL
REFER MOUNTPOINT
copperbowl/ROOT/Waterfox@2020-03-20-06:19:45 67.0M - 59.2G -
copperbowl
On Sat, Jul 02, 2016 at 09:26:14AM +0300, Ivan Klymenko wrote:
> On Sat, 2 Jul 2016 06:19:58 +
> Glen Barber wrote:
> ivan@nonamehost:/ % ftp
> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/11.0-ALPHA6 Trying
> 77.88.40.106:21 ... Connected to ftp.geo.freebsd.org.
>
On Sat, 2 Jul 2016 06:19:58 +
Glen Barber wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> New FreeBSD development branch installation ISOs and virtual machine
> disk images have been uploaded to the FTP mirrors.
>
> As with any development branch, the i
On Sat, Jun 25, 2016 at 02:13:24AM +, Glen Barber wrote:
> New FreeBSD development branch installation ISOs and virtual machine
> disk images have been uploaded to the FTP mirrors.
>
There have been a few reports of "missing" files on the FTP mirrors.
This happened last week with the i386 MA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
New FreeBSD development branch installation ISOs and virtual machine
disk images have been uploaded to the FTP mirrors.
As with any development branch, the installation snapshots are not
intended for use on production systems. We do, however
; o 11.0-ALPHA4 armv6 CUBOX-HUMMINGBOARD
> > > > o 11.0-ALPHA4 armv6 GUMSTIX
> > > > o 11.0-ALPHA4 armv6 RPI-B
> > > > o 11.0-ALPHA4 armv6 RPI2
> > > > o 11.0-ALPHA4 armv6 PANDABOARD
> > > > o 11.0-ALPHA4 armv6 WANDBOARD
> > > >
PI2
> > > o 11.0-ALPHA4 armv6 PANDABOARD
> > > o 11.0-ALPHA4 armv6 WANDBOARD
> > > o 11.0-ALPHA4 aarch64 GENERIC
> > >
> > > Hello.
> > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/11.0-ALPHA4/
> > > not have manifest file.
> o 11.0-ALPHA4 armv6 CUBOX-HUMMINGBOARD
> > o 11.0-ALPHA4 armv6 GUMSTIX
> > o 11.0-ALPHA4 armv6 RPI-B
> > o 11.0-ALPHA4 armv6 RPI2
> > o 11.0-ALPHA4 armv6 PANDABOARD
> > o 11.0-ALPHA4 armv6 WANDBOARD
> > o 11.0-ALPHA4 aarch64 GENERIC
> >
> >
I2
> o 11.0-ALPHA4 armv6 PANDABOARD
> o 11.0-ALPHA4 armv6 WANDBOARD
> o 11.0-ALPHA4 aarch64 GENERIC
>
> Hello.
> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/11.0-ALPHA4/ not have
> manifest file.
>
Huh. Yep, this is a problem.
Thank you for the report. I'll investigate what happened here.
Glen
signature.asc
Description: PGP signature
Please add the MANIFEST file to
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/11.0-ALPHA4/
Thanks!
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "fr
ent branch, the installation snapshots are not
intended for use on production systems. We do, however, encourage
testing on non-production systems as much as possible.
Please also consider installing the sysutils/panicmail port, which can
help in providing FreeBSD developers the necessary information
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
New FreeBSD development branch installation ISOs and virtual machine
disk images have been uploaded to the FTP mirrors.
As with any development branch, the installation snapshots are not
intended for use on production systems. We do, however
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
New FreeBSD development branch installation ISOs and virtual machine
disk images have been uploaded to the FTP mirrors.
As with any development branch, the installation snapshots are not
intended for use on production systems. We do, however
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
New FreeBSD development branch installation ISOs and virtual machine
disk images have been uploaded to the FTP mirrors.
As with any development branch, the installation snapshots are not
intended for use on production systems. We do, however
On 2016-05-23 10:10, Sergey Manucharian wrote:
> Excerpts from Allan Jude's message from Sun 22-May-16 23:55:
>> On 2016-05-22 23:33, Sergey Manucharian wrote:
>>> Is there any materialistic definition of those builds, which
>>> become snapshots at [0]?
Excerpts from Allan Jude's message from Sun 22-May-16 23:55:
> On 2016-05-22 23:33, Sergey Manucharian wrote:
> > Is there any materialistic definition of those builds, which
> > become snapshots at [0]?
> >
> > - Sergey
> >
> > [0] ftp://ftp.freeb
On 2016-05-22 23:33, Sergey Manucharian wrote:
> Is there any materialistic definition of those builds, which
> become snapshots at [0]?
>
> - Sergey
>
> [0] ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/11.0/
>
> _
Is there any materialistic definition of those builds, which
become snapshots at [0]?
- Sergey
[0] ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/11.0/
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo
files, dirs (code 3) at
util.c(1101) [Receiver=3.1.1]
Exit 3
Turns out that if the snapshots are hidden, then getcwd() errors out?
Setting snapdir=visible on the volume gets it to do its job.
As does changing out of the snapshot directory and using the full path
for source and destination
Is this
4-bootonly.iso)
> >>>> on IBM HS22 blade via bladecenter's kvm but I faced with problem on
> >>>> checksum stage, bootonly doesn't contain base, kernel,etc distributions
> >>>> but it contain manifest file.
> >>>> On mirrors we hav
-11.0-CURRENT-amd64-20150302-r279514-bootonly.iso)
on IBM HS22 blade via bladecenter's kvm but I faced with problem on
checksum stage, bootonly doesn't contain base, kernel,etc distributions
but it contain manifest file.
On mirrors we have pub/FreeBSD/snapshots/${ARCH}/11.0-CURRENT/*t
l FreeBSD CURRENT from bootonly image
> >> ( FreeBSD-11.0-CURRENT-amd64-20150302-r279514-bootonly.iso)
> >> on IBM HS22 blade via bladecenter's kvm but I faced with problem on
> >> checksum stage, bootonly doesn't contain base, kernel,etc distributions
> >
faced with problem on checksum
stage, bootonly doesn't contain base, kernel,etc distributions but it contain
manifest file.
On mirrors we have pub/FreeBSD/snapshots/${ARCH}/11.0-CURRENT/*txz and
MANIFEST, sha256 sums from _local_ manifest doesn't match sha256 sums for
fetched files. I suppose
d with problem on checksum
> stage, bootonly doesn't contain base, kernel,etc distributions but it contain
> manifest file.
> On mirrors we have pub/FreeBSD/snapshots/${ARCH}/11.0-CURRENT/*txz and
> MANIFEST, sha256 sums from _local_ manifest doesn't match sha256 sums for
2-r279514-bootonly.iso)
>> on IBM HS22 blade via bladecenter's kvm but I faced with problem on checksum
>> stage, bootonly doesn't contain base, kernel,etc distributions but it contain
>> manifest file.
>> On mirrors we have pub/FreeBSD/snapshots/${ARCH}/11.0-CURRENT/*tx
ed with problem on checksum
> stage, bootonly doesn't contain base, kernel,etc distributions but it contain
> manifest file.
> On mirrors we have pub/FreeBSD/snapshots/${ARCH}/11.0-CURRENT/*txz and
> MANIFEST, sha256 sums from _local_ manifest doesn't match sha256 sums fo
but it contain
manifest file.
On mirrors we have pub/FreeBSD/snapshots/${ARCH}/11.0-CURRENT/*txz and
MANIFEST, sha256 sums from _local_ manifest doesn't match sha256 sums for
fetched files. I suppose it will be fine with RELEASE bootonly iso but not with
stable/current.
there is 2 ways how
Dears All ,
Is it possible to include the link for FreeBSD mirrors list
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html
into
"New FreeBSD snapshots available : ..."
messages ?
This link will prevent a search of this list and will encourage use of
mirrors
FreeBSD 10.0-BETA3 snapshots are now available. These images are
generated from r258657 of stable/10, and are intended as pre -BETA4
snapshots for public testing, until 10.0-BETA4 is rolled (which should
be within the next few days).
Please note, freebsd-update(8) upgrades are not available for
On Sat, 8 Jun 2013, Glen Barber wrote:
The problem is creating the gpart(8) partition scheme on the md(4)
device.
Below follows script(1) output of what the make-memstick.sh script does:
Script started on Sun Jun 9 00:41:08 2013
root@snap:/snap/releng # chroot /snap/releng/10-i386-snap
roo
t in reality, they
> gj> are not.
> gj>
> gj> So, for the snapshots case, the solution is to write the memstick image
> gj> from outside of the chroot environment, which is easy to do because
> gj> I already do this for creating the VM disk images (interestingly
On Sat, Jun 08, 2013 at 02:18:48PM -0500, Nathan Whitehorn wrote:
> On 06/08/13 14:17, Glen Barber wrote:
> > On Sat, Jun 08, 2013 at 12:10:16PM -0700, Tim Kientzle wrote:
> >> On Jun 8, 2013, at 10:34 AM, Glen Barber wrote:
> >>
> >>> On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
>
On 06/08/13 14:17, Glen Barber wrote:
> On Sat, Jun 08, 2013 at 12:10:16PM -0700, Tim Kientzle wrote:
>> On Jun 8, 2013, at 10:34 AM, Glen Barber wrote:
>>
>>> On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
> Has anyone else tried the i386 memstick and having the same problem?
>>>
Tim Kientzle wrote
in <926ef579-8ac9-4a98-8a81-4e978a627...@kientzle.com>:
ti>
ti> On Jun 8, 2013, at 10:34 AM, Glen Barber wrote:
ti>
ti> > On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
ti> >>> Has anyone else tried the i386 memstick and having the same problem?
ti> >>>
ti> >>
t
t fails
gj> entirely. So, the paritions appear to be created, but in reality, they
gj> are not.
gj>
gj> So, for the snapshots case, the solution is to write the memstick image
gj> from outside of the chroot environment, which is easy to do because
gj> I already do this for creating t
On Sat, Jun 08, 2013 at 12:10:16PM -0700, Tim Kientzle wrote:
>
> On Jun 8, 2013, at 10:34 AM, Glen Barber wrote:
>
> > On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
> >>> Has anyone else tried the i386 memstick and having the same problem?
> >>>
> >>
> >> Hmm. Thanks for the re
On Jun 8, 2013, at 10:34 AM, Glen Barber wrote:
> On Fri, Jun 07, 2013 at 05:22:56PM -0400, Glen Barber wrote:
>>> Has anyone else tried the i386 memstick and having the same problem?
>>>
>>
>> Hmm. Thanks for the report. I'll take a look at the logs for i386, but
>> they are generated the sa
ith gpart(8). This is where things blow up.
Because the userland is 32-bit and the kernel is 64-bit, "something"
goes wrong, but interestingly not wrong enough that the script fails
entirely. So, the paritions appear to be created, but in reality, they
are not.
So, for the snapshots ca
On 06/07/13 22:51, Jimmy wrote:
Greetings -
I had originally started playing with the 10-CURRENT amd64 release
a couple of months ago (no complaints here - keep up the good work!)
and had used the memstick snapshot to set things up back then with
no problems.
Now I'd like to wipe everything and
On Fri, Jun 07, 2013 at 03:51:29PM -0500, Jimmy wrote:
> Greetings -
>
> I had originally started playing with the 10-CURRENT amd64 release
> a couple of months ago (no complaints here - keep up the good work!)
> and had used the memstick snapshot to set things up back then with
> no problems.
>
Greetings -
I had originally started playing with the 10-CURRENT amd64 release
a couple of months ago (no complaints here - keep up the good work!)
and had used the memstick snapshot to set things up back then with
no problems.
Now I'd like to wipe everything and switch to the i386 version, but
t
Before the introduction of async_destroy I wrote a script to destroy
ZFS snapshots in parallel to speed up the process. It's available at:
http://www.fabiankeil.de/sourcecode/zfs-snapshot-destroyer/zsd.pl
A couple of years ago the only downside seemed to be that it
requires more memory and
Am 10/06/12 03:32, schrieb Bruce Cran:
> On 05/10/2012 15:29, Miroslav Lachman wrote:
>> Unofficial snapshots can be downloaded from
>> https://pub.allbsd.org/FreeBSD-snapshots/ for a long time
>> (bootonly.iso too)
>
> I'm baffled as to why those aren't just
On Fri, Oct 05, 2012 at 04:29:45PM +0200, Miroslav Lachman wrote:
> It would be nice to have them hosted on FreeBSD.org site as official
> source.
I agree 100%.
> Unofficial snapshots can be downloaded from
> https://pub.allbsd.org/FreeBSD-snapshots/ for a long time (bootonly.iso t
On 05/10/2012 15:29, Miroslav Lachman wrote:
Unofficial snapshots can be downloaded from
https://pub.allbsd.org/FreeBSD-snapshots/ for a long time
(bootonly.iso too)
I'm baffled as to why those aren't just made official.
--
Bruce Cran
_
Glen Barber wrote:
Hi,
A number of FreeBSD users have displayed interest in the availability
and testing of -STABLE and -CURRENT snapshot releases.
I have been working on generating snapshots regularly, and now would
like to announce their availability for those interested in testing.
Please
Hi,
A number of FreeBSD users have displayed interest in the availability
and testing of -STABLE and -CURRENT snapshot releases.
I have been working on generating snapshots regularly, and now would
like to announce their availability for those interested in testing.
Please note, as always with
> https://pub.allbsd.org/FreeBSD-snapshots/
i have been unable to boot i386 and am64 isos from late last week.
randy
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
On 09/14/2012 23:43, Randy Bush wrote:
> ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-arch is a bit empty. i
> guess things are moving around. any idea where i can get the latest
> tag=.
I and others have brought up this issue repeatedly over the last couple
of years, and the PTB have decided th
> As I said, this is the latest snapshot. Long story short is that the
> old process was changed before 9.0 and releng hasn't caught up with
> the new process yet in a sustainable manner (at least, not executing
> it on a regular basis). If you have interest in making sure regular
> (monthly) relea
On Fri, Sep 14, 2012 at 11:55 PM, Randy Bush wrote:
>>> ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-arch is a bit empty. i
>>> guess things are moving around. any idea where i can get the latest
>>> tag=.
>>
>> Latest tag is 9.1-RC1:
>> ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/9.1
On 15-09-2012 15:43, Randy Bush wrote:
> ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-arch is a bit empty. i
> guess things are moving around. any idea where i can get the latest
> tag=.
https://pub.allbsd.org/FreeBSD-snapshots/
--
Joel
__
>> ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-arch is a bit empty. i
>> guess things are moving around. any idea where i can get the latest
>> tag=.
>
> Latest tag is 9.1-RC1:
> ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/9.1-RC1/ , etc.
this is for an i386 running 10-current
rand
On Fri, Sep 14, 2012 at 11:43 PM, Randy Bush wrote:
> ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-arch is a bit empty. i
> guess things are moving around. any idea where i can get the latest
> tag=.
Latest tag is 9.1-RC1:
ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/9.1-RC1/ , etc.
-
Randy Bush wrote:
> ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-arch is a bit empty. i
> guess things are moving around. any idea where i can get the latest
> tag=.
cut and paste error
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots
___
freebs
ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-arch is a bit empty. i
guess things are moving around. any idea where i can get the latest
tag=.
randy
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
T
> First step in debugging is to find out if the problem is SU+J
> specific. To find out, turn off SU+J but leave SU. This change
> is done by running:
>
> umount
> tunefs -j disable
> mount
> cd
> rm .sujournal
Success! Th
On Wed, Jan 11, 2012 at 11:12:35PM +0530, Gautam Mani wrote:
>
> Do let me know if I can try something further.
>
I reproduced this again and here is the core.txt crash summary if it
helps.
http://pastebin.com/hTGMXX6A
Thanks
Gautam
___
freebsd-curre
On Wed, Jan 11, 2012 at 10:30:39AM +0100, Yamagi Burmeister wrote:
> Hello,
> I've done some tests to verify that the problem only occures when SU+J
> is used, but not SU without J. In fact, I did run the following two
> loops on different TTYs in parallel:
I also confirm this using a similar tech
an 2012 18:30:51 +0100
> > From: Yamagi Burmeister
> > To: j...@freebsd.org, mckus...@freebsd.org
> > Cc: freebsd-current@freebsd.org, br...@bryce.net
> > Subject: Re: FS hang when creating snapshots on a UFS SU+J setup
> >
> > Hello,
> >
> >
gt; et
> Subject: Re: FS hang when creating snapshots on a
> UFS SU+J setup
>
> > Hello,
> >
> > I'm sorry to bother you, but you may not be aware of
> this thread and
> this problem. We are several people experiencing
> deadlocks, kernel
> panics and other
> Date: Mon, 9 Jan 2012 18:30:51 +0100
> From: Yamagi Burmeister
> To: j...@freebsd.org, mckus...@freebsd.org
> Cc: freebsd-current@freebsd.org, br...@bryce.net
> Subject: Re: FS hang when creating snapshots on a UFS SU+J setup
>
> Hello,
>
> I'm sorry to bother
Hello,
I'm sorry to bother you, but you may not be aware of this thread and
this problem. We are several people experiencing deadlocks, kernel
panics and other problems when creating sanpshots on file systems
with SU+J. It would be nice to get some feedback, e.g. how can we
help debugging and / or
1 - 100 of 186 matches
Mail list logo
