From owner-freebsd-questions@FreeBSD.ORG Fri Jul 17 02:29:52 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0DB6D1065672 for ; Fri, 17 Jul 2009 02:29:52 +0000 (UTC) (envelope-from tajudd@gmail.com) Received: from mail-yx0-f181.google.com (mail-yx0-f181.google.com [209.85.210.181]) by mx1.freebsd.org (Postfix) with ESMTP id BECDC8FC0C for ; Fri, 17 Jul 2009 02:29:51 +0000 (UTC) (envelope-from tajudd@gmail.com) Received: by yxe11 with SMTP id 11so964685yxe.3 for ; Thu, 16 Jul 2009 19:29:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=4YDxe5jx9U/fO2EdzH6wZUhBqf10YtdfnInmZGqRZu4=; b=Z0suDOVblsGcbD+K0R0pkG88roPiqtNcyXfTY0YiMFvCIPfZAZCttvmgb2LmBBPA2s iwv4KQ0nuAZ8fhANqeNfl4DDmXMk9NzvRnBPRLnxzlUy1026lOsM77++GrCU70xZLzRp Y4ynlHOG//uLZfX7sIY1A2eGe2Vxl18BDXfKA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=nPtHvD0KPO1YV+PNYU8FxuwvC6M26b7GfuYrBZKy2Pnj+Ha0xzakpHlVf3nFtaqQXn zNdew4axhffvH8SNDTirN6VFdjtSi9qoHMSqIk/mr13IGqT1MyQ9arSb7a1hq738hZgw of5AKU6fWpxw4L5AeUj+HhD9T9yl4ZbAWdCqs= MIME-Version: 1.0 Received: by 10.100.208.8 with SMTP id f8mr810744ang.42.1247797790998; Thu, 16 Jul 2009 19:29:50 -0700 (PDT) Date: Thu, 16 Jul 2009 20:29:50 -0600 Message-ID: From: Tim Judd To: freebsd-questions Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: unionfs X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jul 2009 02:29:52 -0000 I've got an odd problem, and I'm puzzled why it's so puzzling. At home, my router serves as a basic single-client diskless server. Been working beautifully with no issues. Filesystems mount as expected and operations are as quick as expected as the server who's servicing it. The diskless fstab tells to mount the following: server:/diskless / nfs ro 0 0 md /var.mfs mfs rw,-M,-s=256m 0 0 /var.mfs /var unionfs rw 0 0 Everything works beautifully, no errors. Kernel is 7.2R-p2 I copied this exact fstab, to a new hardware firewall and it fails to accomplish the same task. /dev/ad0s1a / ufs ro 0 0 md /var.mfs mfs rw,-M,-s=64m 0 0 /var.mfs /var unionfs rw 0 0 Kernel is standard 7.2R kernel, no changes Two changes only: root is on a hard disk as UFS instead of NFS memory filesystem (which mounts) is only 64M However, when 7.2-RELEASE (unpatched so far) boots, it fails to mount the unionfs /var.mfs (upper) on top of /var (lower). The error returned is "mount_unionfs: /var: operation not supported by device" Any clues? anything you need? I'd appreciate any straws to reach for. --Tim