| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
PR: 151321
Submitted by: Simon Walton
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
big sector size. When gctl error is set gctl_has_param() always returns
'false', which prevents geli(8) from finding some arguments and also masks
an error, which is generates in such case.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was needed for recover implementation.
Implement the recover command for GPT. Now GPT will marked as
corrupt when any of three types of corruption will be detected:
1. Damaged primary GPT header or table
2. Damaged secondary GPT header or table
3. Secondary header is not located in the last LBA
Marked GPT becomes read-only. Any changes with corrupt table
are prohibited. Only "destroy" and "recover" commands are allowed.
Discussed with: geom@ (mostly silence)
Tested by: Ilya A. Arhipov
Approved by: mav (mentor)
MFC after: 2 weeks
|
|
|
|
|
| |
Submitted by: arundel
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
initialize all the data. This is huge waste of time and resources if
there were no writes yet, as there is no real data to synchronize.
Optimize this by sending "virgin" argument to secondary, which gives it a hint
that synchronization is not needed.
In the common case (where noth nodes are configured at the same time) instead
of synchronizing everything, we don't synchronize at all.
MFC after: 1 week
|
|
|
|
|
|
| |
name exists.
MFC after: 3 days
|
|
|
|
|
|
| |
no need to make then visible from outside.
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
Found with: valgrind
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
| |
It's a bit more pedantic regarding .Bl list elements. This has an added
benefit of unbreaking the ipfw(8) manpage, where groff was silently
skipping one list element.
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before this change if you wanted to suspend your laptop and be sure that your
encryption keys are safe, you had to stop all processes that use file system
stored on encrypted device, unmount the file system and detach geli provider.
This isn't very handy. If you are a lucky user of a laptop where suspend/resume
actually works with FreeBSD (I'm not!) you most likely want to suspend your
laptop, because you don't want to start everything over again when you turn
your laptop back on.
And this is where geli suspend/resume steps in. When you execute:
# geli suspend -a
geli will wait for all in-flight I/O requests, suspend new I/O requests, remove
all geli sensitive data from the kernel memory (like encryption keys) and will
wait for either 'geli resume' or 'geli detach'.
Now with no keys in memory you can suspend your laptop without stopping any
processes or unmounting any file systems.
When you resume your laptop you have to resume geli devices using 'geli resume'
command. You need to provide your passphrase, etc. again so the keys can be
restored and suspended I/O requests released.
Of course you need to remember that 'geli suspend' won't clear file system
cache and other places where data from your geli-encrypted file system might be
present. But to get rid of those stopping processes and unmounting file system
won't help either - you have to turn your laptop off. Be warned.
Also note, that suspending geli device which contains file system with geli
utility (or anything used by 'geli resume') is not very good idea, as you won't
be able to resume it - when you execute geli(8), the kernel will try to read it
and this read I/O request will be suspended.
|
|
|
|
|
|
| |
already allows both device names and nodes to be specified.
Reviewed by: avg
|
|
|
|
|
|
| |
No change in rendered output, less mandoc lint warnings.
Tool provided by: Nobuyuki Koganemaru n-kogane at syd.odn.ne.jp
|
|
|
|
|
| |
Submitted by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
Submitted by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 3 days
|
| |
|
|
|
|
| |
Reported by: pluknet
|
|
|
|
|
|
|
| |
- Ensure that the error message is NUL-terminated before printing it.
PR: bin/147482
MFC after: 2 weeks
|
|
|
|
|
|
| |
Suggested by: kib
Approved by: kib (mentor)
MFC after: 5 days
|
|
|
|
|
|
|
|
| |
cope. Skip multiple spaces in a few contexts.
PR: 96854
Submitted by: Shin'ya Kumabuchi
MFC after: 1 week
|
|
|
|
|
|
|
| |
once during start-up.
Reported by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
error messages, so when we clean up after child process, we have to check if
the event socketpair is still there.
Submitted by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 3 days
|
|
|
|
| |
They have no effect when coming in pairs, or before .Bl/.Bd
|
|
|
|
|
|
| |
and there can be some garbage from the stack.
MFC after: 1 week
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
Reported by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
I'm unable to reproduce the race described in comment anymore and also the
comment is incorrect - localfd represents local component from configuration
file, eg. /dev/da0 and not HAST provider.
Reported by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 1 week
|
|
|
|
|
|
| |
signals every 5 seconds and not every 10 seconds as before.
MFC after: 3 days
|
|
|
|
|
|
| |
argument is redundant, remove it.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
masking it.
This fixes bogus reports about hooks running for too long and other problems
related to garbage-collecting child processes.
Reported by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
fstab(5) format requires that one of "rw", "rq" or "ro" is always
specified.
PR: bin/123021
Reviewed by: keramida, rodrigc
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
list other schemes attributes.
Reviewed by: simon, rpaulo
MFC after: 2 weeks
|
|
|
|
| |
Approved by: kib (mentor)
|
|
|
|
|
| |
Submitted by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
This is especially useful for things like installers, where regular
geli prompt can't be used.
- Add support for specifing multiple -K or -k options, so there is no
need to cat all keyfiles and read them from standard input.
Requested by: Kris Moore <kris@pcbsd.org>, thompsa
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Large (60GB) filesystems created using "newfs -U -O 1 -b 65536 -f 8192"
show incorrect results from "df" for free and used space when mounted
immediately after creation. fsck on the new filesystem (before ever
mounting it once) gives a "SUMMARY INFORMATION BAD" error in phase 5.
This error hasn't occurred in any runs of fsck immediately after
"newfs -U -b 65536 -f 8192" (leaving out the "-O 1" option).
Solution:
The default UFS1 superblock is located at offset 8K in the filesystem
partition; the default UFS2 superblock is located at offset 64K in
the filesystem partition. For UFS1 filesystems with a blocksize of
64K, the first alternate superblock resides at 64K which is the the
location used for the default UFS2 superblock. By default, the
system first checks for a valid superblock at the default location
for a UFS2 filoesystem. For a UFS1 filesystem with a blocksize of
64K, there is a valid UFS1 superblock at this location. Thus, even
though it is expected to be a backup superblock, the system will
use it as its default superblock. So, we have to ensure that all the
statistcs on usage are correct in this first alternate superblock
as it is the superblock that will actually be used.
While tracking down this problem, another limitation of UFS1 became
evident. For UFS1, the number of inodes per cylinder group is stored
in an int16_t. Thus the maximum number of inodes per cylinder group
is limited to 2^15 - 1. This limit can easily be exceeded for block
sizes of 32K and above. Thus when building UFS1 filesystems, newfs
must limit the number of inodes per cylinder group to 2^15 - 1.
Reported by: Guy Helmer<ghelmer@palisadesys.com>
Followup by: Bruce Cran <brucec@freebsd.org>
PR: 107692
MFC after: 4 weeks
|
|
|
|
|
|
|
|
|
|
|
|
| |
This option doesn't passed to kernel and handled in user-space.
With -F option gpart creates new "delete" request for each
partition in table. Each request has flags="X" that disables
auto-commit feature. Last request is the original "destroy" request.
It has own flags and can have disabled or enabled auto-commit feature.
If error is occurred when deleting partitions, then new "undo" request
is created and all changes will be rolled back.
Approved by: kib (mentor)
|
|
|
|
|
|
|
|
| |
- Don't use u_char and u_int in userland.
- Change 'unsigned' to 'unsigned int'.
- Update copyright years.
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
| |
- Flush write cache after each write.
MFC after: 1 week
|
|
|
|
|
|
| |
- fsync() created filed.
MFC after: 1 week
|
|
|
|
|
|
|
| |
don't want situation where old size is equal to new size, as we will trash
newly written metadata.
MFC after: 1 week
|
|
|
|
|
|
| |
- Flush cache after writing metadata.
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
This way the primary process inherits signal mask from the main process,
which fixes a race where signal is delivered to the primary process before
configuring signal mask.
Reported by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 3 days
|