NetBSD Problem Report #48526

From jnemeth@CornerstoneService.ca  Thu Jan 16 01:56:09 2014
Return-Path: <jnemeth@CornerstoneService.ca>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "Postmaster NetBSD.org" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id CAC16A6475
	for <gnats-bugs@gnats.NetBSD.org>; Thu, 16 Jan 2014 01:56:09 +0000 (UTC)
Message-Id: <201401160156.s0G1u3CK005756@server.cornerstoneservice.ca>
Date: Wed, 15 Jan 2014 17:56:03 -0800 (PST)
From: jnemeth@CornerstoneService.ca
Reply-To: jnemeth@CornerstoneService.ca
To: gnats-bugs@gnats.NetBSD.org
Subject: dumpdates name field too short
X-Send-Pr-Version: 3.95

>Number:         48526
>Category:       bin
>Synopsis:       dumpdates name field too short
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jan 16 02:00:00 +0000 2014
>Originator:     John Nemeth
>Release:        applies to any release/-current through 2014/01/15
>Organization:
>Environment:
>Description:
	DUMPOUTFMT/DUMPINFMT in include/protocols/dumprestore.h
specifies the format of lines in /etc/dumpdates.  They specify that
the first field which is the name of the filesystem should be 16
characters long.  This is much too short for dm(4) devices which
is what backs LVM devices.  These devices have names starting with
"/dev/mapper/" which is already 12 characters, and the final path
component is a logical name which can be anything.
>How-To-Repeat:
	dump -u a filesystem with a long name
>Fix:
	It would be a simple matter to expand the field width, but
this would create an incompatibility with existing /etc/dumpdates
files.  Whether this would be a problem and what to do about it is
an open question.

Home	PR Database Search