headers
Patrick Mahan | 25 May 22:46

GEOM: ada0: corrupt or invalid

All,

First - These are FreeBSD 9.0

I am experiencing an unusual problem brought on because I used
dd(1) to close a boot drive.  We are setting up some demo systems
to ship to our VARs and we initially used HP Proliants with
WD 300 GB drives.  But management decided to go with a Dell towers
(power edge?) instead.  These new drives are only 80 GB, so I
tried to use dd to only copy the first 80 GB since it did not
look like the usage on the WD's were under 80 GB.

However, after the dd and boot of the Dell box I am seeing the
following:

ada0 at ata2 bus 0 scbus2 target 0 lun 0
ada0: <WDC WD800JD-75JNA0 05.01C05> ATA-6 SATA 1.x device
ada0: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 8192bytes)
ada0: 76293MB (156250000 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad4

GEOM: ada0: corrupt or invalid GPT detected.
GEOM: ada0: GPT rejected -- may not be recoverable.

And the boxes will not boot since they cannot find the kernel,
etc.

I booted the install media and switched to live-cd.  That's where
I found the error for the ada0 device.  Looking at the /dev
directory, I don't seen and of the partitions (a, b, c, etc).  Also,
(Continue reading)

Permalink | Reply | 3 comments |
headers
Mark Felder | 25 May 15:24
Favicon

UFS SUJ and fsck questions

Hi guys,

I'm building out a highly available storage backend with HAST+NFS on UFS.  
So far I've encountered a node going down and the filesystem being dirty,  
so the other side won't mount it automatically. I've resolved this issue  
with the following before the mount:

fsck -C -t ufs -y /dev/hast/${disk}

However, the problem is that on a disk nearly 1TB in size it will take a  
long time to fsck and the failover won't be as smooth. SUJ would fit the  
bill here pretty well. My main issue is not understanding the interaction  
between SUJ and fsck.

If I simply try to mount a fs with SUJ, it will do the SUJ magic if  
necessary and move on. But what if it's damaged beyond what SUJ can handle  
and needs a real fsck? Can I use the same procedure? Will executing `fsck  
-C` against an SUJ enabled filesystem that hasn't run the SUJ journal yet  
do that first and exit if the journal replay was successful? If not, does  
anyone have any ideas on how I can detect that automatically so I can get  
the filesystem mounted cleanly without human intervention?

Thanks!
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
=?utf-8?Q? "Germ=C3=A1n_M._Bravo" ?= | 24 May 15:40
Picon
Gravatar

Re: kern/161511: [unionfs] Filesystem deadlocks when using multiple unionfs mounts on top of single filesystem

The following reply was made to PR kern/161511; it has been noted by GNATS.

From: =?utf-8?Q?"Germ=C3=A1n_M._Bravo"?= <german.mb <at> gmail.com>
To: "bug-followup <at> FreeBSD.org" <bug-followup <at> FreeBSD.org>,
 "gcooper <at> ixsystems.com" <gcooper <at> ixsystems.com>
Cc:  
Subject: Re: kern/161511: [unionfs] Filesystem deadlocks when using multiple unionfs mounts on top of
single filesystem
Date: Thu, 24 May 2012 08:34:25 -0500

 I can verify this patch absolutely fixes all the issues I was experiencing. M=
 y problem was random deadlocking behavior, forcing me to reboot the system m=
 anually, when I started/stopped jails using unionfs and/or starting services=
  inside said jails, under FreeBSD 9 RELEASE.=
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
Andrey Simonenko | 24 May 13:47
Picon

NLM uses AUTH_SYS ignoring sec option in mount_nfs

Hello,

Looks like that NLM always uses AUTH_SYS even if a client specified
another security flavor in the mount_nfs's "sec" option.  Also NLM
on the server does not verify that NLM client's security flavor
is allowed by NFS exported file system, security flavors array from
VFS_CHECKEXP() is ignored in nlm/nlm_prot_impl.c:nlm_get_vfs_state().

Such behaviour of NLM I see on 10-CURRENT, I added log messages to
the kernel to see security flavors used by NFSv3 and NLM requests.
Both NFS client and server are on the same system, NFSv3 mounts are
from unprivileged users.

According to [1] NLMv4 allows to use different security flavors.

Can somebody comment such behaviour of NLM?

[1] http://pubs.opengroup.org/onlinepubs/9629799/chap14.htm
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 2 comments |
headers
bsalinux@gmail.com | 22 May 20:35
Picon

NFS Server Limiting open port RST response

Hi,

I have a FreeBSD + ZFS server configured as NFS server. This server is
being used to store regressions that are generated over a period of
2-3 days. Time to time nfs would drop the mount and the program fails
to find the output directory (nfs automount). On the other hand if I
use Linux NFS server to host this space, I see no issues.

Time to time I see messages like these in the logs:

Limiting open port RST response from 334 to 200 packets/sec

It seems that the automount dismounts the server while the regressions
are being computed and the output is idle. I even kept one terminal
window open on the compute server that is "cd" into the output
directory so that it prevents the dismounting the automount but it
still fails.

Do I need to tweak any parameters? Can I stop dismounting (from NFS
server side)?

Any help would be appreciated.

Thanks.
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
(Continue reading)

Permalink | Reply | 3 comments |
headers
FreeBSD bugmaster | 21 May 13:07
Picon
Favicon

Current problem reports assigned to freebsd-fs <at> FreeBSD.org

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o kern/168158  fs         [zfs] incorrect parsing of sharenfs options in zfs (fs
o kern/167979  fs         [ufs] DIOCGDINFO ioctl does not work on 8.2 file syste
o kern/167977  fs         [smbfs] mount_smbfs results are differ when utf-8 or U
o kern/167905  fs         [zfs] zfs set canmount=on UNMOUNTS dataset
o kern/167688  fs         [fusefs] Incorrect signal handling with direct_io
o kern/167685  fs         [zfs] ZFS on USB drive prevents shutdown / reboot
o kern/167612  fs         [portalfs] The portal file system gets stuck inside po
o kern/167272  fs         [zfs] ZFS Disks reordering causes ZFS to pick the wron
o kern/167266  fs         [zfs] [nfs] ZFS + new NFS export (sharenfs) leads to N
o kern/167260  fs         [msdosfs] msdosfs disk was mounted the second time whe
o kern/167109  fs         [zfs] [panic] zfs diff kernel panic Fatal trap 9: gene
o kern/167105  fs         [nfs] mount_nfs can not handle source exports wiht mor
o kern/167067  fs         [zfs] [panic] ZFS panics the server
o kern/167066  fs         [zfs] ZVOLs not appearing in /dev/zvol
o kern/167065  fs         [zfs] boot fails when a spare is the boot disk
o kern/167048  fs         [nfs] [patch] RELEASE-9 crash when using ZFS+NULLFS+NF
o kern/166912  fs         [ufs] [panic] Panic after converting Softupdates to jo
o kern/166851  fs         [zfs] [hang] Copying directory from the mounted UFS di
o kern/166566  fs         [zfs] zfs split renders 2 disk (MBR based) mirror unbo
o kern/166477  fs         [nfs] NFS data corruption.
o kern/165950  fs         [ffs] SU+J and fsck problem
(Continue reading)

Permalink | Reply | 0 comments |
headers
linimon | 21 May 10:32
Picon
Favicon

Re: kern/168158: [zfs] incorrect parsing of sharenfs options in zfs (fsshare.c)

Old Synopsis: incorrect parsing of sharenfs options in zfs (fsshare.c)
New Synopsis: [zfs] incorrect parsing of sharenfs options in zfs (fsshare.c)

Responsible-Changed-From-To: freebsd-bugs-≥freebsd-fs
Responsible-Changed-By: linimon
Responsible-Changed-When: Mon May 21 08:32:13 UTC 2012
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=168158
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
gleb | 20 May 14:35
Picon
Favicon

Re: kern/139597: [patch] [tmpfs] tmpfs initializes va_gen but doesn't update it on vnode change

Synopsis: [patch] [tmpfs] tmpfs initializes va_gen but doesn't update it on vnode change

State-Changed-From-To: open->
State-Changed-By: gleb
State-Changed-When: Sun May 20 12:32:55 UTC 2012
State-Changed-Why: 
Not a bug, only ZFS updates generation number.

http://www.freebsd.org/cgi/query-pr.cgi?pr=139597
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
Martin Birgmeier | 20 May 10:10
Picon

Re: kern/136865: [nfs] [patch] NFS exports atomic and on-the-fly atomic updates

The following reply was made to PR kern/136865; it has been noted by GNATS.

From: Martin Birgmeier <Martin.Birgmeier <at> aon.at>
To: bug-followup <at> FreeBSD.org, simon <at> comsys.ntu-kpi.kiev.ua
Cc:  
Subject: Re: kern/136865: [nfs] [patch] NFS exports atomic and on-the-fly
 atomic updates
Date: Sun, 20 May 2012 10:04:01 +0200

 Dear Andrey,

 It seems that you have done some great work here, and I would really 
 like to see this integrated into the core FreeBSD distribution (I was 
 the submitter of http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/131342).

 I would like to try out your patches and have two questions:

 - Do your patches support multiple zfs sharenfs specifications as 
 proposed in http://www.freebsd.org/cgi/query-pr.cgi?pr=147881 (I am 
 using this)?

 - Could you give a concise list of incompatibilities (and even 
 regressions if they should exist at all) of your solution compared to 
 the standard one? - As to the advantages, I am already convinced. :-)

 Thank you & regards,

 Martin

_______________________________________________
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mateusz Guzik | 19 May 22:22
Picon

[patch] Broken RLIMIT_FSIZE handling in ZFS

Hello,

vn_rlimit_fsize takes uio->uio_offset and uio->uio_resid into account
when determining whether given write would exceed RLIMIT_FSIZE.

When APPEND flag is specified, ZFS updates uio->uio_offset to point to the
end of file.

But this happens after a call to vn_rlimit_fsize, so vn_rlimit_fsize check
can be rendered ineffective by thread that opens some file with O_APPEND
and lseeks below RLIMIT_FSIZE before calling write.

This fixes the problem for me:
http://student.agh.edu.pl/~mjguzik/patches/zfs-rlimit-fsize.patch

Slightly modified testcase stolen from pr standards/164793:
http://student.agh.edu.pl/~mjguzik/patches/writelimit.c

Without the patch this testacase will just finish by producing 80000 bytes
file on ZFS.

On UFS it gives the following output:
failed when adding 27 bytes after 59994 bytes (error: File too large)

Same happens on ZFS with the patch.

--

-- 
Mateusz Guzik <mjguzik gmail.com>
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
(Continue reading)

Permalink | Reply | 0 comments |
headers
Edgar Fuß | 19 May 18:50
Picon
Favicon

Book on FFS

Is there a book (or other documentation) about FFS giving more details than the 4.4BSD bible?

I'm writing a Perl script that takes a subset of newfs's arguments, reads a find -ls output and computes the
fragmentation/bookkeeping overhead for that particular data set. (The intent is to find out how much the
newfs parameters actually matter in terms of overhead for that given data set.)

In the course of researching what the exact overhead for the free list, inodes and CG heads is, I learned
(from discussions on NetBSD's tech-kern list and from reading ufs/ffs/fs.h and mkfs.c) various
"interesting" things like files that need indirect blocks not being allocated fragments, "number of
blocks" and "number of data blocks" (i.e. fs_size and fs_dsize) being in units of fragments, not blocks. I
suspect there is way more for me to learn in this field._______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |

Gmane