FreeBSD Project Quarterly Status Report - Third Quarter 2020
Introduction
This report covers FreeBSD related projects for the period between July
and September, and is the third of four planned reports for 2020.
This quarter brings a good mix of additions and changes to the FreeBSD
Thanks for the tip! I've fixed the issue following the following steps:
1) added two new disks with the same size: da3 and da4
2) Made a partition for both:
gpart create -s gpt da3
gpart create -s gpt da4
gpart add -t freebsd-zfs da3
gpart add -t freebsd-zfs da4
3) replace both disks on pool
I very much doubt that there's any remotely sane way to re-partition da1 &
da2 while they are in the pool.
If you carefully edit the output of the 'gpart backup' command, you
probably can use 'gpart restore' to partition da1 and da2. Read the
'gpart' man page very carefully, if you aren't
Walter,
Yes, gpt/disk0 is da0. I can do the partition backup booting from livecd.
But is there a way to make the partition of da1 and da2 since both are
already inserted on pool? I think it's not allowed...
Thanks.
On Wed, Oct 21, 2020 at 5:18 PM Walter Cramer wrote:
> My guess - there is a
My guess - there is a work-around or two, but you'll face a lot more
grief, long-term, if you don't do things the right way (aka do a bunch of
re-install work) now.
I'd start with 'gpart backup da0' (guessing that gpt/disk0 is on da0), to
see how the original disk is partitioned. Then
Hi guys,
Thank your for your answer.
@Ricchard First of all I didn't have a chance to run zpool upgrade, because
after the system update reboot i ran into the issue.
@Walter and @mike Regarding making a partition, I never see any
recommendation about this, I've been always using the entire disk
Just a guess, Is your VM still trying to boot from whatever gpt/disk0 is
? Or is it perhaps trying to boot from da1 or da2 which does not have
boot info ? Generally its not recommended to use the entire disk as
part of a pool. Create a partition scheme first
gpart create -s gpt da1
gpart add -t
On Wed, 21 Oct 2020 18:28:44 +0300
Konstantin Belousov wrote:
> >
> > kdump with MAP_STACK.
> >
> > 87183 polyimport CALL
> > mmap(0,0x1000,0x3,0x1402,0x,0,0)
> > 87183 polyimport RET mmap -1 errno 22 Invalid argument
> So it is anything but 'insufficient memory' (I suspected
On Wed, Oct 21, 2020 at 06:18:50PM +0300, Nick Kostirya via freebsd-stable
wrote:
> On Wed, 21 Oct 2020 17:16:57 +0300
> Konstantin Belousov wrote:
>
> > On Wed, Oct 21, 2020 at 04:53:11PM +0300, Nick Kostirya via freebsd-stable
> > wrote:
> > > Hello.
> > > I have question about mmap.
> > >
On Wed, 21 Oct 2020 17:16:57 +0300
Konstantin Belousov wrote:
> On Wed, Oct 21, 2020 at 04:53:11PM +0300, Nick Kostirya via freebsd-stable
> wrote:
> > Hello.
> > I have question about mmap.
> >
> > void *OSMem::AllocateDataArea(size_t )
> > {
> > // Round up to an integral number of
On Wed, Oct 21, 2020 at 04:53:11PM +0300, Nick Kostirya via freebsd-stable
wrote:
> Hello.
> I have question about mmap.
>
> void *OSMem::AllocateDataArea(size_t )
> {
> // Round up to an integral number of pages.
> space = (space + pageSize-1) & ~(pageSize-1);
> int fd = -1; // This
Hello.
I have question about mmap.
void *OSMem::AllocateDataArea(size_t )
{
// Round up to an integral number of pages.
space = (space + pageSize-1) & ~(pageSize-1);
int fd = -1; // This value is required by FreeBSD. Linux doesn't care
int flags = MAP_PRIVATE | MAP_ANON;
#ifdef
Hi there,
Anyone can help please? I've many servers with this same issue. Thanks
On Fri, Oct 16, 2020 at 10:24 AM Cassiano Peixoto
wrote:
> Hi there,
>
> I have a FreeBSD 12.1-STABLE running on VMWARE with one disk. Then I added
> two more disks to expand my pool. BTW I already did it many
13 matches
Mail list logo
