Re: Problems adding Intel 750 to zfs pool

[dy...@techtangents.com]

I found this:
https://lists.freebsd.org/pipermail/freebsd-fs/2015-February/020828.html

Seems to be related to vfs.zfs.vdev.trim_on_init - I turn this off and 
it adds immediately.




dy...@techtangents.com 
18 July 2015 2:35 pm
Hi,

I've installed an Intel 750 400GB NVMe PCIe SSD in a Dell R320 running 
FreeBSD 10.2-beta-1... not STABLE, but not far behind, I think. 
Apologies if this is the wrong mailing list, or if this has been fixed 
in STABLE since the beta.


Anyway, I've gparted it into 2 partitions - 16GB for slog/zil and 
357GB for l2arc. Adding the slog partition to the pool takes about 2 
minutes - machine seems hung during that time. Ping works, but I can't 
open another ssh session.


Adding the l2arc doesn't seem to complete - it's been going 10 minutes 
now and nothing. Ping works, but I can't log in to the local console 
or another ssh session.


I'm adding the partitions using their gpt names. i.e.
zpool add zroot log gpt/slog
zpool add zroot cache gpt/l2arc

The system BIOS is up-to-date. The OS was a fresh 10.1 install, then 
freebsd-update to 10.2-beta2. 10.1 exhibited the same symptoms.


Root is on zfs.

Device was tested to be working on Windows 8.1 on a Dell T1700 
workstation.


Any ideas?

Cheers,

Dylan Just


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problems adding Intel 750 to zfs pool

[dy...@techtangents.com]

Hi,

I've installed an Intel 750 400GB NVMe PCIe SSD in a Dell R320 running 
FreeBSD 10.2-beta-1... not STABLE, but not far behind, I think. 
Apologies if this is the wrong mailing list, or if this has been fixed 
in STABLE since the beta.


Anyway, I've gparted it into 2 partitions - 16GB for slog/zil and 357GB 
for l2arc. Adding the slog partition to the pool takes about 2 minutes - 
machine seems hung during that time. Ping works, but I can't open 
another ssh session.


Adding the l2arc doesn't seem to complete - it's been going 10 minutes 
now and nothing. Ping works, but I can't log in to the local console or 
another ssh session.


I'm adding the partitions using their gpt names. i.e.
zpool add zroot log gpt/slog
zpool add zroot cache gpt/l2arc

The system BIOS is up-to-date. The OS was a fresh 10.1 install, then 
freebsd-update to 10.2-beta2. 10.1 exhibited the same symptoms.


Root is on zfs.

Device was tested to be working on Windows 8.1 on a Dell T1700 workstation.

Any ideas?

Cheers,

Dylan Just

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

wine

[henannk30]

Dear :

We come from ZHOUZHENG,HENAN PROVINCE of CHINA. According to the need of 
company developing, we are interested in your wine. China is a huge market and 
has many consumers. I bet your wine will be popular through our cooperation. We 
need order 2 bottles

of white wine , 4 bottles of red wine and every bottle is 750ml.Please let 
us know your price.

LOOKING FORWARD TO OUR COOPERATION.

Thank you

Contact: su zhi jun

Address: zhengzhou wenhua road 18 # in china

Telephone: 0086-15538325676










___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

FreeBSD 10.2-BETA2 Now Available

[Glen Barber]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The second BETA build of the 10.2-RELEASE release cycle is now
available.

Installation images are available for:

o amd64 GENERIC
o i386 GENERIC
o ia64 GENERIC
o powerpc GENERIC
o powerpc64 GENERIC64
o sparc64 GENERIC

The image checksums follow at the end of this email.

FreeBSD/arm SD card images are available for:

o BEAGLEBONE
o CUBOX-HUMMINGBOARD
o GUMSTIX
o RPI-B
o PANDABOARD
o WANDBOARD

Note:  For convenience for those without console access to supported arm
devices, a default 'freebsd' user exists for ssh(1) login.  The password
is 'freebsd', which it is strongly recommended to change after gaining
access to the system.  Additionally, the 'root' user password is 'root',
which is also recommended to change.

All images can be downloaded from:

  ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.2/

If you notice problems you can report them through the Bugzilla PR
system or on the -stable mailing list.

If you would like to use SVN to do a source based update of an existing
system, use the "stable/10" branch.

A list of changes since 10.1-RELEASE are available on the stable/10
release notes:

  https://www.freebsd.org/relnotes/10-STABLE/relnotes/article.html

Please note, the release notes page is not yet complete, and will be
updated on an ongoing basis as the 10.2-RELEASE cycle progresses.

=== Changes Since 10.2-BETA1 ===

o [arm] The missing GEOM_LABEL in the GUMSTIX and PANDABOARD kernel
  configuration files that prevented the '/dev/ufs/rootfs' fstab(5)
  entry to mount the root filesystem has been fixed.

o Correctly handle rare events of transient write errors to the cylinder
  group blocks.

o An incorrect implementation of kvasprintf() in the Linux compatibility
  and emulation code has been fixed.

o Setting the initial system clock time for systems with a CMOS clock
  set before the year 2000 has been fixed.

o The pw(8) utility has been updated to allow creating users with UID 0,
  in addition to other miscellaneous updates.

o The MIB names in the 'user' sysctl(3) tree have been fixed to no
  longer return '0' or empty values.

o The lo(4) driver has been updated to fix an issue where pcap(3) and
  bpf(4) would fail when writing to the interface.

o The watchdog(4) device has been fixed to print to the correct buffer.

o [arm] The '/var/log' and '/var/tmp' directories are no longer mounted
  as md(4)-backed devices, which would cause messages from syslogd(8)
  and other applications from retaining log files after reboot(8).

o A kernel bug that would cause various issues on systems without
  a battery-backed clock has been fixed.

o The ntp suite has been updated to version 4.2.8p3.

o The port and protocol information for IPSEC are now included in the
  SADB_ACQUIRE message as required by RFC 2367.

o Fix the issue with devices requiring memory below 4G (such as USB
  controllers), unable to initialize on very large memory machines (64G
  or more).

=== Virtual Machine Disk Images ===
 
VM disk images are available for the amd64 and i386 architectures.
Disk images may be downloaded from the following URL (or any of the
FreeBSD FTP mirrors):

  ftp://ftp.freebsd.org/pub/FreeBSD/releases/VM-IMAGES/10.2-BETA2/

The partition layout is:

 ~ 512k - freebsd-boot GPT partition type (bootfs GPT label)
 ~ 1GB  - freebsd-swap GPT partition type (swapfs GPT label)
 ~ ~17GB - freebsd-ufs GPT partition type (rootfs GPT label)

The disk images are available in QCOW2, VMDK, and raw disk image formats
The image download size is approximately 135 MB, which decompress to a
20GB sparse image.

Note:  An issue preventing the VHD-formatted images from booting was
discovered during the BETA1 build, which is still being investigated.

Note to consumers of the dvd1.iso image: The bsdconfig(8) utility cannot
install the packages included on the DVD, however they can be installed
manually.

To install packages from the dvd1.iso installer, create and mount the
/dist directory:

# mkdir -p /dist
# mount -t cd9660 /dev/cd0 /dist

Replace '/dev/cd0' with the appropriate cd(4) device as necessary.

Next, bootstrap pkg(8) from the DVD: 

# env REPOS_DIR=/dist/packages/repos \
  pkg bootstrap

At this point, pkg-install(8) can be used to install additional packages
from the DVD.  Please note, the REPOS_DIR environment variable should be
used each time using the DVD as the package repository, otherwise
conflicts with packages from the upstream mirrors may occur when they
are fetched.  For example, to install Gnome and Xorg, run:

# env REPOS_DIR=/dist/packages/repos \
  pkg install xorg-server xorg gnome3 [...]

=== Amazon EC2 AMI Images ===

FreeBSD/amd64 EC2 AMIs are available in the following regions:

 us-east-1 region: ami-77f1201c
 us-west-1 region: ami-a9fd0fed
 us-west-2 region: ami-41999b71
 sa-east-1 region: ami-ddff70c0
 eu-west-1 region: ami-76175e01
 eu-central-1 region: ami-ca8db7d7
 ap-northeast-1 r

Re: jail: /etc/rc: cannot create /dev/null: Operation not supported

[Per olof Ljungmark]

On 2015-07-17 01:41, James Gritton wrote:
> On 2015-07-15 13:52, Per olof Ljungmark wrote:
>> FreeBSD 10.2-PRERELEASE #0 r284949
>>
>> The jail can be started, but when /etc/rc is executed:
>>
>> root@mar:/ # sh -x /etc/rc
>> + stty status ^T
>> /etc/rc: cannot create /dev/null: Operation not supported
>> + trap : 2
>> + trap 'echo '\''Boot interrupted'\''; exit 1' 3
>> + HOME=/
>> + PATH=/sbin:/bin:/usr/sbin:/usr/bin
>> + export HOME PATH
>> + [ '' = autoboot ]
>> + autoboot=no
>> + _boot=quietstart
>> + /sbin/sysctl -n vfs.nfs.diskless_valid
>> /etc/rc: cannot create /dev/null: Operation not supported
>> ...
>>
>> I have done the procedure several times before but never saw this one
>> before and don't know how to get around it.
>>
>> Ideas anyone? Any recent changes that can show up like the above?
>>
>> Thanks!
> 
> If it's trying to create /dev/null, I assume that the jail's /dev isn't
> mounted when /etc/rc is running.  Do you have mount.devfs set in the
> jail.conf, or jail_foo_devfs_enable in rc.conf (depending on your
> configuration)? For that matter, can you tell if the jail's /dev is
> mounted?
> 
> - Jamie

Yes, it's mounted.

Because I can set up jails with an identical procedure on other boxes we
run I suspect something is wrong with the install so I am starting from
scratch with this one.

While doing that, I am trying to sort another problem, namely to boot
zfs on root on a HP Proliant with a P410 controller, but that is another
story.

You know, if it was easy it would not be interesting...

Thanks!

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"