Hello, Freebsd-current.
Maybe, everything is reported already, but I think, that better I'll
be second, that no-one notice this:
Manual partitioning chosen
(1) Installer offer me bunch of Partition schemes, but only MBR
and BSD have sense. Why i386 installer offer me PC98 or PowerPC-based
Ap
Le Thu, 18 Aug 2011 10:22:31 +0100,
Hugo Silva a écrit :
Hello,
> I'm wondering. On a virtual machine (amd64 HVM+PV), it's crashing
> every time. Not sure if this is SNAFU, as I had never used ufs
> snapshots on freebsd before.
>
> After running mksnap_ffs, ssh stops working (a telnet session
VirtualBox Version: 4.0.12_OSE r72916
uname -a: FreeBSD shuttle0.lan 9.0-BETA1 FreeBSD 9.0-BETA1 #1: Wed Aug
17 01:21:47 WEST 2011
net...@shuttle0.lan:/usr/obj/usr/src/sys/GALILEO amd64
The kernel panic is occurred when I start a virtual machine with boot
from CD/DVD burner/reader device.
With
Ashley Williams wrote:
> walltimestamp and timestamp don't appear to be right in BETA-1:
>
>
> # dtrace -qn 'syscall::exec*:return { printf("%Y
> %s\n",walltimestamp,curpsinfo->pr_psargs); }'
> 1970 Jan 1 10:00:00 date
> 1970 Jan 1 10:00:00 ping
> 1970 Jan 1 10:00:00 ls
I can reproduce this
On 2011-08-18 18:30, Christoph Hoffmann wrote:
...
Changing the order of execution in zfsboot.c main() function to
[…]
int
main(void)
{
[…]
bios_getmem();
if (high_heap_size> 0) {
[…]
bootinfo.bi_version = BOOTINFO_VERSION;
bootinfo.bi_size = sizeof(bootinfo);
bootinfo
Hiroki Sato wrote:
> Rick Macklem wrote
> in <1565511281.69213.1313764157732.javamail.r...@erie.cs.uoguelph.ca>:
>
> rm> Hiroki Sato wrote:
> rm> > fsid_guid = dmu_objset_fsid_guid(zfsvfs->z_os);
> rm> > ASSERT((fsid_guid & ~((1ULL<<56)-1)) == 0);
> rm> > vfsp->vfs_fsid.val[0] = fsid_guid;
> rm>
Hiroki Sato wrote:
> Rick Macklem wrote
> in <1565511281.69213.1313764157732.javamail.r...@erie.cs.uoguelph.ca>:
>
> rm> Hiroki Sato wrote:
> rm> > fsid_guid = dmu_objset_fsid_guid(zfsvfs->z_os);
> rm> > ASSERT((fsid_guid & ~((1ULL<<56)-1)) == 0);
> rm> > vfsp->vfs_fsid.val[0] = fsid_guid;
> rm>
On Sat, 20 Aug 2011, Rick Macklem wrote:
Yes, using vfs_getnewfsid() does not solve the issue.
I noticed that Solaris looked up a fixed array vfssw[] exactly for
the purpose. I think a table like it is a good solution for fixing
fsid for each file system.
-- Hiroki
If anyone thinks using a fi
Hi,
I have an nfs server running 9-current. Everything works as far
as nfs i/o operations are concerned.
From another FreeBSD box, nfs locking works great to the server
when addressed by both it's real ip address and it's aliased ip
address.
From a Linux system:
Linux bb05d6403.unx.sas
