date:20151126

Re: Resizing a zpool as a VMware ESXi guest ...

2015-11-26 Thread Matthew Grooms


On 10/16/2014 3:10 AM, Edward Tomasz Napierała wrote:

On 1010T1529, Matthew Grooms wrote:

All,

I am a long time user and advocate of FreeBSD and manage a several
deployments of FreeBSD in a few data centers. Now that these
environments are almost always virtual, it would make sense that FreeBSD
support for basic features such as dynamic disk resizing. It looks like
most of the parts are intended to work. Kudos to the FreeBSD foundation
for seeing the need and sponsoring dynamic increase of online UFS
filesystems via growfs. Unfortunately, it would appear that there are
still problems in this area, such as ...

a) cam/geom recognizing when a drive's size has increased
b) zpool recognizing when a gpt partition size has increased

For example, if I do an install of FreeBSD 10 on VMware using ZFS, I see
the following ...

root@zpool-test:~ #  gpart show
=>  34  16777149  da0  GPT  (8.0G)
  34  10241  freebsd-boot  (512K)
1058   41943042  freebsd-swap  (2.0G)
 4195362  125818213  freebsd-zfs  (6.0G)

If I increase the VM disk size using VMware to 16G and rescan using
camcontrol, this is what I see ...

"camcontrol rescan" does not force fetching the updated disk size.
AFAIK there is no way to do that.  However, this should happen
automatically, if the "other side" properly sends proper Unit Attention
after resizing.  No idea why this doesn't happen with VMWare.
Reboot obviously clears things up.

[..]


Now I want the claim the additional 14 gigs of space for my zpool ...

root@zpool-test:~ # zpool status
pool: zroot
   state: ONLINE
scan: none requested
config:

  NAME  STATE READ
WRITE CKSUM
  zroot ONLINE 0 0 0
gptid/352086bd-50b5-11e4-95b8-0050569b2a04  ONLINE 0 0 0

root@zpool-test:~ # zpool set autoexpand=on zroot
root@zpool-test:~ # zpool online -e zroot
gptid/352086bd-50b5-11e4-95b8-0050569b2a04
root@zpool-test:~ # zpool list
NAMESIZE  ALLOC   FREECAP  DEDUP  HEALTH  ALTROOT
zroot  5.97G   876M  5.11G14%  1.00x  ONLINE  -

The zpool appears to still only have 5.11G free. Lets reboot and try
again ...

Interesting.  This used to work; actually either of those (autoexpand or
online -e) should do the trick.


root@zpool-test:~ # zpool set autoexpand=on zroot
root@zpool-test:~ # zpool online -e zroot
gptid/352086bd-50b5-11e4-95b8-0050569b2a04
root@zpool-test:~ # zpool list
NAMESIZE  ALLOC   FREECAP  DEDUP  HEALTH  ALTROOT
zroot  14.0G   876M  13.1G 6%  1.00x  ONLINE  -

Now I have 13.1G free. I can add this space to any of my zfs volumes and
it picks the change up immediately. So the question remains, why do I
need to reboot the OS twice to allocate new disk space to a volume?
FreeBSD is first and foremost a server operating system. Servers are
commonly deployed in data centers. Virtual environments are now
commonplace in data centers, not the exception to the rule. VMware still
has the vast majority of the private virutal environment market. I
assume that most would expect things like this to work out of the box.
Did I miss a required step or is this fixed in CURRENT?

Looks like genuine bugs (or rather, one missing feature and one bug).
Filling PRs for those might be a good idea.



All,

I know this is a very late follow up, but spent some more time looking 
at this today and found some additional information that I found quite 
interesting. I setup two VMs, one that acts as an iSCSI initiator ( 
CURRENT ) and another that acts as a target ( 10.2-RELEASE ). Both are 
running under ESXi v5.5. There are two block devices on the initiator, 
da1 and da2, that I used for resize testing ...


[root@iscsi-i /home/mgrooms]# camcontrol devlist
   at scbus1 target 0 lun 0 (cd0,pass0)
  at scbus2 target 0 lun 0 (pass1,da0)
  at scbus2 target 1 lun 0 (pass2,da1)
 at scbus3 target 0 lun 0 (da2,pass3)

The da1 device is a virtual disk hanging off of a VMware virtual SAS 
controller ...


[root@iscsi-i /home/mgrooms]# pciconf
...
mpt0@pci0:3:0:0:class=0x010700 card=0x197615ad chip=0x00541000 
rev=0x01 hdr=0x00

vendor = 'LSI Logic / Symbios Logic'
device = 'SAS1068 PCI-X Fusion-MPT SAS'
class  = mass storage
subclass   = SAS

[root@iscsi-i /home/mgrooms]# camcontrol readcap da1 -h
Device Size: 10 G, Block Length: 512 bytes

[root@iscsi-i /home/mgrooms]# gpart show da1
=>  40  20971440  da1  GPT  (10G)
40  209714401  freebsd-ufs  (10G)

The da2 device is an iSCSI LUN mounted from my FreeBSD 10.2 VM running 
ctld ...


[root@iscsi-i /home/mgrooms]# iscsictl
Target name  Target portalState
iqn.2015-01.lab.shrew:target0iscsi-t.shrew.lab Connected: da2

[root@iscsi-i /home/mgrooms]# camcontrol readcap da2 -h
Device Size: 10 G, Block Length: 512 bytes

[root@iscsi-i /home/mgrooms]# gpart show da2
=>  40

RE: freebsd-current compile with clang & ccache

2015-11-26 Thread M - Krasznai András

Hi

I am now reading the manual pages for src.conf. 

Src.conf should only be used to specify variables for make, e.g. 
WITHOUT_PROFILE, or WITH_CCACHE_BUILD. Man src.conf does not say much more 
about ccache, but ccache-howto-freebsd says that WITH_CCACHE_BUILD is only for 
building ports with ccache; for world and kernel you should set CC and CXX 
variables within make.conf following the advice in ccache-howto 

("To use ccache for ports, just add WITH_CCACHE_BUILD=yes to /etc/make.conf.

To use ccache for base add the following to /etc/make.conf:

.if (!empty(.CURDIR:M/usr/src*) || !empty(.CURDIR:M/usr/obj*))
.if !defined(NOCCACHE) && exists(/usr/local/libexec/ccache/world/cc)
CC:=${CC...

")

I do not copy here the full howto

My problem is that after a successful compile of base - world and kernel - 
using ccache I run make installkernel correctly, but after reboot and 
mergemaster -p I got a lot of ccache error messages during make installworld. 
They complain ebout not finding compiler cc in path although cc -v gives the 
clang version number, so cc IS on the path.

Best regards

András Krasznai

-Original Message-
From: owner-freebsd-curr...@freebsd.org 
[mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of Rainer Hurling
Sent: 2015. november 25. 20:48
To: Bryan Drewery; FreeBSD-Current
Subject: Re: freebsd-current compile with clang & ccache

Am 25.11.15 um 20:37 schrieb Bryan Drewery:
> On 11/25/2015 11:34 AM, Rainer Hurling wrote:
>> Am 25.11.15 um 19:50 schrieb Bryan Drewery:
>>> On 11/25/2015 10:09 AM, Juan Molina wrote:
> On 11/24/2015 1:31 AM, M - Krasznai András wrote:
>> /What can I do to eliminate the ccache error during installworld
> apart from not using ccache? /
> I would recommend not setting CC or CCACHE_PATH in make.conf and 
> using the new WITH_CCACHE_BUILD=yes option instead.
>
> --
> Regards,
> Bryan Drewery

 Hi.

 I'm seeing the same ccache errors and I do not have CC or 
 CCACHE_PATH defined anywhere. Only WITH_CCACHE_BUILD and WITH_FAST_DEPEND 
 in src.conf.

>>>
>>> WITH_FAST_DEPEND is not related.
>>>
>>> Are you building and installing as a different user? Using a 
>>> different MAKEOBJDIRPREFIX in build and install?
>>>
>>> Do you have CCACHE_PATH in your environment?
>>>
>>> Run 'make ccache-print-options|grep path'. It should have no value.
>>>
>>
>> Is there any possibility to redirect the .ccache directory, something 
>> like CCACHE_PATH for userland?
>>
>> I am asking, because in my attempts to build base with 
>> WITH_CCACHE_BUILD and WITH_FAST_DEPEND enabled, it breaks with error 
>> message 'file system full'. My root partition has only 1GB and ccache 
>> itself seems to need more than 800MB in /root/.ccache.
>>
> 
> You want to modify CCACHE_DIR. You can do this in make.conf or the 
> environment.
> 
> I tend to just symlink /root/.ccache to somewhere else though and let 
> the default work via the symlink.
> 
> Also see 'man src.conf' (WITH_CCACHE_BUILD section) and 'man ccache'.
> 

Oops, I should have looked into man src.conf before asking here, sorry.

And many thanks for the quick and helpful answer.
___
freebsd-current@freebsd.org mailing list 
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: freebsd-current compile with clang & ccache

2015-11-26 Thread Juan Ramón Molina Menor


Le 25/11/2015 22:11, Bryan Drewery a écrit :

On 11/25/2015 12:59 PM, Juan Ramón Molina Menor wrote:

Le 25/11/2015 19:50, Bryan Drewery a écrit :

On 11/25/2015 10:09 AM, Juan Molina wrote:

On 11/24/2015 1:31 AM, M - Krasznai András wrote:

/What can I do to eliminate the ccache error during installworld

apart from not using ccache? /
I would recommend not setting CC or CCACHE_PATH in make.conf and using
the new WITH_CCACHE_BUILD=yes option instead.

--
Regards,
Bryan Drewery

Hi.

I’m seeing the same ccache errors and I do not have CC or CCACHE_PATH
defined anywhere. Only WITH_CCACHE_BUILD and WITH_FAST_DEPEND in
src.conf.


WITH_FAST_DEPEND is not related.

OK, thanks. I was referring to the content of /etc/src.conf. By the way,
there is no /etc/make.conf in this system.


Are you building and installing as a different user? Using a different
MAKEOBJDIRPREFIX in build and install?

Not at all, just following the /etc/src/UPDATING instructions, as root:

# cd /usr/src
# svn up
# make -j2 buildworld
# make -j2 kernel

# mergemaster -Fp
# make installworld COMPILER_TYPE="clang"

# mergemaster -Fi
# make delete-old


Do you have CCACHE_PATH in your environment?

Yes, it is set in /etc/csh.cshrc as indicate the ccache instructions:

# echo $CCACHE_PATH
/usr/bin:/usr/local/bin


Run 'make ccache-print-options|grep path'. It should have no value.

# make ccache-print-options | grep path
(environment) path =



Which branch and revision is this?


 11.0-CURRENT r291280 (yesterday).
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RE: freebsd-current compile with clang & ccache

2015-11-26 Thread M - Krasznai András

Hi

I now modified my setup according to the links you provided I and compile a 
freshly updated base of FreeBSD-Current.

I will report when finshed.

Rgds

András

-Original Message-
From: NGie Cooper [mailto:yaneurab...@gmail.com] 
Sent: 2015. november 26. 8:36
To: M - Krasznai András
Cc: Bryan Drewery; freebsd-current@freebsd.org
Subject: Re: freebsd-current compile with clang & ccache

> On Nov 25, 2015, at 23:21, M - Krasznai András  
> wrote:
> 
> Thanks, but as far as I know WITH_CCACHE_BUILD is only for ports compilation 
> and novadays I use binary ports wherever I can.

It’s available in recent versions of FreeBSD CURRENT [1], [2] .
Cheers,
-NGie

1. https://lists.freebsd.org/pipermail/freebsd-arch/2015-November/017472.html
2. https://svnweb.freebsd.org/changeset/base/290526
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Aheros AR9565: buffer error messages from ath_edma_rxbuf_alloc and ath_edma_rxfifo_alloc

2015-11-26 Thread José Pérez


Hi Adrian,
ATH_ENABLE_11N was missing from kernel config, now it works perfectly, 
sorry for the noise.


Here's the sysct output FYI:
Nov 26 19:10:12 current kernel: no tx bufs (empty list): 0
Nov 26 19:10:12 current kernel: no tx bufs (was busy): 0
Nov 26 19:10:12 current kernel: aggr single packet: 33
Nov 26 19:10:12 current kernel: aggr single packet w/ BAW closed: 0
Nov 26 19:10:12 current kernel: aggr non-baw packet: 94
Nov 26 19:10:12 current kernel: aggr aggregate packet: 12684
Nov 26 19:10:12 current kernel: aggr single packet low hwq: 2439
Nov 26 19:10:12 current kernel: aggr single packet RTS aggr limited: 0
Nov 26 19:10:12 current kernel: aggr sched, no work: 24419
Nov 26 19:10:12 current kernel: 0:  0  1:  0  2:   
3453  3:138
Nov 26 19:10:12 current kernel: 4: 45  5: 39  6:   
2721  7:   4245
Nov 26 19:10:12 current kernel: 8:337  9:225 10:
110 11: 90
Nov 26 19:10:12 current kernel: 12:236 13: 54 14:
104 15: 47
Nov 26 19:10:12 current kernel: 16: 57 17: 48 18:
 80 19: 73
Nov 26 19:10:12 current kernel: 20: 46 21: 64 22:
 65 23: 62
Nov 26 19:10:12 current kernel: 24: 35 25: 69 26:
 25 27: 83
Nov 26 19:10:12 current kernel: 28: 62 29: 38 30:
 23 31:  4
Nov 26 19:10:12 current kernel: 32:  6 33:  0 34:
  0 35:  0
Nov 26 19:10:12 current kernel: 36:  0 37:  0 38:
  0 39:  0
Nov 26 19:10:12 current kernel: 40:  0 41:  0 42:
  0 43:  0
Nov 26 19:10:12 current kernel: 44:  0 45:  0 46:
  0 47:  0
Nov 26 19:10:12 current kernel: 48:  0 49:  0 50:
  0 51:  0
Nov 26 19:10:12 current kernel: 52:  0 53:  0 54:
  0 55:  0
Nov 26 19:10:12 current kernel: 56:  0 57:  0 58:
  0 59:  0
Nov 26 19:10:12 current kernel: 60:  0 61:  0 62:
  0 63:  0

Nov 26 19:10:12 current kernel:
Nov 26 19:10:12 current kernel: HW TXQ 0: axq_depth=0, axq_aggr_depth=0, 
axq_fifo_depth=0, holdingbf=0
Nov 26 19:10:12 current kernel: HW TXQ 1: axq_depth=0, axq_aggr_depth=2, 
axq_fifo_depth=3, holdingbf=0
Nov 26 19:10:12 current kernel: HW TXQ 2: axq_depth=0, axq_aggr_depth=0, 
axq_fifo_depth=0, holdingbf=0
Nov 26 19:10:12 current kernel: HW TXQ 3: axq_depth=0, axq_aggr_depth=0, 
axq_fifo_depth=0, holdingbf=0
Nov 26 19:10:12 current kernel: HW TXQ 8: axq_depth=0, axq_aggr_depth=0, 
axq_fifo_depth=0, holdingbf=0
Nov 26 19:10:12 current kernel: Total TX buffers: 413; Total TX buffers 
busy: 0 (413)
Nov 26 19:10:12 current kernel: Total mgmt TX buffers: 32; Total mgmt TX 
buffers busy: 0
Nov 26 19:10:12 current kernel: 0: fifolen: 16/16; head=0; tail=0; 
m_pending=0, m_holdbf=0
Nov 26 19:10:12 current kernel: 1: fifolen: 128/128; head=71; tail=71; 
m_pending=0, m_holdbf=0
Nov 26 19:10:12 current kernel: Total RX buffers in free list: 368 
buffers


Regards,

---
José Pérez

El 2015-11-25 01:18, Adrian Chadd escribió:

Hm, what's in your kenrel config file? Is ENABLE_11N or whatever the
ath driver option there?

sysctl dev.ath.0.txagg=1 ; then check dmesg and output me the results.

Thanks!


-a


On 24 November 2015 at 14:50, José Pérez  wrote:

Dear Svatopluk,
tried again with current, and I get (almost) the same:
Nov 23 18:14:47 current kernel: ath0: ath_edma_rxbuf_alloc: nothing on
rxbuf?!
Nov 23 18:14:47 current kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc
failed: i=0, nbufs=128?
Nov 23 18:14:47 current kernel: ath0: ath_edma_rxbuf_alloc: nothing on
rxbuf?!
Nov 23 18:14:47 current kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc
failed: i=1, nbufs=128?

Ideas? Can I help?

Thank you.

Regards,


---
José Pérez


El 2015-11-23 13:45, Svatopluk Kraus escribió:


On Mon, Nov 23, 2015 at 1:12 PM, José Pérez  wrote:


Hi,
I am the (happy?) owner of an Atheros AR9565 which used to work just
fine.

I recently updated an old -current, and a flood of these messages 
bumped

up:
Nov 13 17:47:16 test kernel: ath0: ath_edma_rxbuf_alloc: nothing on
rxbuf?!
Nov 13 17:47:16 test kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc
failed:
i=24, nb
ufs=128?

# pciconf -lv | relevant_part
ath0@pci0:1:0:0:class=0x028000 card=0x064211ad 
chip=0x0036168c

rev=0x01 hdr=0x00
vendor = 'Qualcomm Atheros'
device = 'QCA9565 / AR9565 Wireless Network Adapter'
class  = network

# dmesg | relevant_part
ath0:  mem 0xf080-0xf087 irq 32 at
device
0.0 on pci1
ath0: WB335 2-ANT card detected
ar9300_attach: calling ar9300_hw_attach
ar9300_hw_attach: calling ar9300_eeprom_attach
ar9300_flash_map: unimplemented for now
Restoring Cal data from DRAM
Restoring Cal data from EEPROM
Restoring Cal data from Flash

Re: Resizing a zpool as a VMware ESXi guest ...

RE: freebsd-current compile with clang & ccache

Re: freebsd-current compile with clang & ccache

RE: freebsd-current compile with clang & ccache

Re: Aheros AR9565: buffer error messages from ath_edma_rxbuf_alloc and ath_edma_rxfifo_alloc

5 matches

Site Navigation

Mail list logo

Footer information