summaryrefslogtreecommitdiff
path: root/sbin/dump
AgeCommit message (Collapse)Author
2023-06-03bsd.own.mk: rename GCC_NO_* to CC_WNO_*lukem
Rename compiler-warning-disable variables from GCC_NO_warning to CC_WNO_warning where warning is the full warning name as used by the compiler. GCC_NO_IMPLICIT_FALLTHRU is CC_WNO_IMPLICIT_FALLTHROUGH Using the convention CC_compilerflag, where compilerflag is based on the full compiler flag name.
2023-06-03bsd.own.mk: rename to CC_WNO_ADDRESS_OF_PACKED_MEMBERlukem
Provide a single variable CC_WNO_ADDRESS_OF_PACKED_MEMBER with options for both clang and gcc, to replace CLANG_NO_ADDR_OF_PACKED_MEMBER CC_NO_ADDR_OF_PACKED_MEMBER GCC_NO_ADDR_OF_PACKED_MEMBER Using the convention CC_compilerflag, where compilerflag is based on the full compiler flag name.
2022-11-17Restore backward compatibility of UFS2 with previous NetBSD releases bychs
disabling support in UFS2 for extended attributes (including ACLs). Add a new variant of UFS2 called "UFS2ea" that does support extended attributes. Add new fsck_ffs operations "-c ea" and "-c no-ea" to convert file systems from UFS2 to UFS2ea and vice-versa (both of which delete all existing extended attributes in the process).
2022-03-14Silently ignore fstab entries with NAME= entries that cannot be resolved.mlelstv
Fixes PR 56249.
2022-01-26PR/56643: Paul Goyette: Disable the last block adjustment for now. It seemschristos
to break restore.
2021-07-07PR/56270: Matthias Scheler: dump fails on ffsv1: Zero c_extsize since ffsv1christos
does not support extended attributes.
2021-06-19Add external attribute dumping and restoring support from FreeBSD.christos
Does not fully work yet, attributes are being saved and restored correctly, but don't appear in the restored files somehow.
2021-06-07Bitmaps (TS_BITS and TS_CLRI) dont use the "c_addr" array as theyhannken
cannot have holes. As bitmaps are written without TS_ADDR records "c_count" may be larger than the "c_addr" size resulting in a segmentation violation reading "c_addr" beyond its end. Compute "blks" for TS_INODE and TS_ADDR only -- its used for multi volume dumps and the bitmaps must both be on the first volume.
2020-12-03PR bin/55834kre
count blocks written in unsigned 64 bit counter rather than signed int which overflows after 2^31-1 blocks (2TiB) after which neither the 5 minute status updates or SIGINFO (^T) reports are issued until the negative numbers increase past 0 and wildly inaccurate reports would be written.
2020-09-06add support for new GCC 9 warnings that may be too much to fixmrg
right now. new address-of-packed-member and format-overflow warnings have new GCC_NO_ADDR_OF_PACKED_MEMBER amd GCC_NO_FORMAT_OVERFLOW variables to remove these warnings. apply to a bunch of the tree. mostly, these are real bugs that should be fixed, but in many cases, only by removing the 'packed' attribute from some structure that doesn't really need it. (i looked at many different ones, and while perhaps 60-80% were already properly aligned, it wasn't clear to me that the uses were always coming from sane data vs network alignment, so it doesn't seem safe to remove packed without careful research for each affect struct.) clang already warned (and was not erroring) for many of these cases, but gcc picked up dozens more.
2020-04-05Fix depenency on common symbols in sbin.joerg
2019-10-13introduce some common variables for use in GCC warning disables:mrg
GCC_NO_FORMAT_TRUNCATION -Wno-format-truncation (GCC 7/8) GCC_NO_STRINGOP_TRUNCATION -Wno-stringop-truncation (GCC 8) GCC_NO_STRINGOP_OVERFLOW -Wno-stringop-overflow (GCC 8) GCC_NO_CAST_FUNCTION_TYPE -Wno-cast-function-type (GCC 8) use these to turn off warnings for most GCC-8 complaints. many of these are false positives, most of the real bugs are already commited, or are yet to come. we plan to introduce versions of (some?) of these that use the "-Wno-error=" form, which still displays the warnings but does not make it an error, and all of the above will be re-considered as either being "fix me" (warning still displayed) or "warning is wrong."
2019-08-19Add -D flag to allow the user to specify an alternate dumpdates file.perseant
Closes PR #54469.
2019-03-25Bump date for previous.wiz
2019-03-25Add -U flag to dump(8) and dump_lfs(8) to specify dumpdates entrymanu
This address situations where dump(8) cannot figure out the device being dumped. It also allows tracking of subvolume dumps by using virtual device as dumpdates entry.
2019-03-01Use getfsspecname() to fill the filesystem argument in dumpdates.christos
While here, make sure that the error strings terminate with newline consistently, and add a function that adds the system error string.
2019-02-03- mark Exit() __deadmrg
- bump a buffer size to avoid possible truncation - adding missing fallthru comment
2018-07-15Document what rdump is (was once) for. PR 53442.dholland
2016-08-15dump was there from v4.sevan
Confirmed from the TUHS hosted copies of man pages. Bump date.
2015-11-16- update NAME_MAX to match the kernel.christos
- add a comment about where the constant is used.
2015-08-24Consistently use iswap64() and 64bit intermediate variable, as well asbouyer
64bit formats for c_tapea. Fixes tape useage report for large filesystems.
2015-08-24Default the read block size (-k default value) to kern.maxphys (usuallybouyer
64k these days). This gives a noticable performance boost on large filesystems.
2015-08-12Hack up dinode usage to be 64 vs. 32 as needed. Part 1.dholland
(This part changes the native lfs code; the ufs-derived code already has 64 vs. 32 logic, but as aspects of it are unsafe, and don't entirely interoperate cleanly with the lfs 64/32 stuff, pass 2 will be rehashing that.)
2015-07-28Add a new lfs header file: lfs_accessors.h.dholland
This contains all the accessor functions and macros out of lfs.h. Add an include of lfs_accessors.h after all uses of lfs.h... except for code that wants to define its own struct lfs-alike that the accessors are supposed to play along with. For these, set STRUCT_LFS and include lfs_accessors.h after the necessary structure has been defined, so that lfs_accessors.h can emit functions in terms of it.
2015-04-28Fix typosprlw1
2013-09-08Fix handling of NAME aliases in /etc/fstab.mlelstv
2013-06-23fsbtodb() -> FFS_FSBTODB(), EXT2_FSBTODB(), or MFS_FSBTODB()dholland
dbtofsb() -> FFS_DBTOFSB() or EXT2_DBTOFSB() (Christos already did the lfs ones a few days back)
2013-06-19Rename ambiguous macros:dholland
MAXDIRSIZE -> UFS_MAXDIRSIZE or LFS_MAXDIRSIZE NINDIR -> FFS_NINDIR, EXT2_NINDIR, LFS_NINDIR, or MFS_NINDIR INOPB -> FFS_INOPB, LFS_INOPB INOPF -> FFS_INOPF, LFS_INOPF blksize -> ffs_blksize, ext2_blksize, or lfs_blksize sblksize -> ffs_blksize These are not the only ambiguously defined filesystem macros, of course, there's a pile more. I may not have found all the ambiguous definitions of blksize(), too, as there are a lot of other things called 'blksize' in the system.
2013-06-15handle new lfs splitchristos
2013-01-22Stuff UFS_ in front of a few of ufs's symbols to reduce namespacedholland
pollution. Specifically: ROOTINO -> UFS_ROOTINO WINO -> UFS_WINO NXADDR -> UFS_NXADDR NDADDR -> UFS_NDADDR NIADDR -> UFS_NIADDR MAXSYMLINKLEN -> UFS_MAXSYMLINKLEN MAXSYMLINKLEN_UFS[12] -> UFS[12]_MAXSYMLINKLEN (for consistency) Sort out ext2fs's misuse of NDADDR and NIADDR; fortunately, these have the same values in ext2fs and ffs. No functional change intended.
2013-01-13Use __printflike.dholland
2013-01-13Use void * for I/O functions and remove no-longer-needed casts.dholland
2013-01-13Use more static.dholland
2013-01-13Use static; remove unused global var this uncovered.dholland
2013-01-13Use <ctype.h> functions correctly.dholland
2013-01-13Add some const.dholland
2012-08-29Use more markup, fix English usage.dholland
2012-08-10Don't depend on HAVE_GCC being always defined.joerg
2012-05-05remove ancient crapchristos
2012-04-07factor out rawname() from dump, fsck, savecore.christos
2012-04-07use getfsspecname()christos
2012-02-19Sort option descriptions a bit more.wiz
2012-02-19PR/45735: Bug Hunting: The dump(8) manpage, as well as the program's ↵christos
`usage'-line, needs improvement
2011-09-16NULL does not need a cast, hereplunky
2011-08-29Use __deadjoerg
2011-06-20remove most of the remaining HAVE_GCC tests that are always true inmrg
the modern world.
2011-02-24fss(4): Allow FSSIOCSET to set the initial flags. Add a new flaghannken
"FSS_UNLINK_ON_CREATE" to unlink the backing store before the snapshot gets created. With this change dump(8) no longer dumps the zero-sized, but named snapshot it is working on. Same applies to fsck_ffs(8).
2010-11-05File system snapshots are no longer experimental.hannken
2010-05-14Use a list for the list of bugs.jruoho
2010-04-11Add -x option which allows to run `fsck_msdos -n' on a snapshot ofhannken
a live file system. While here modify snap_open() to accept a character device as its first arg and remove now unneeded get_snap_device(). Reviewed by: Manuel Bouyer <bouyer@netbsd.org>