On Fri, 3 Feb 2017, Tinker wrote:
> On 2017-02-04 03:57, Philip Guenther wrote:
> > On Fri, 3 Feb 2017, Tinker wrote:
> > > After rebooting the machine (now in ordinary softdep mode, and fsck did
> > > its job), I tried to do "rm -rf /home/lost+found", and got "ffs_blkfree:
> > > freeing free
On 2017-02-04 03:57, Philip Guenther wrote:
On Fri, 3 Feb 2017, Tinker wrote:
After rebooting the machine (now in ordinary softdep mode, and fsck
did
its job), I tried to do "rm -rf /home/lost+found", and got
"ffs_blkfree:
freeing free block".
...
I'm not so freaked out by this error as
On Fri, 3 Feb 2017, Tinker wrote:
> After rebooting the machine (now in ordinary softdep mode, and fsck did
> its job), I tried to do "rm -rf /home/lost+found", and got "ffs_blkfree:
> freeing free block".
...
> I'm not so freaked out by this error as indeed my FS must have been in a
> badly
On Fri, 3 Feb 2017, Sebastien Marie wrote:
...
> My understanding is if savecore(8) is able to extract bsd.core
> information from swap partition, it means the bsd.core information is
> *not* encrypted by crypto-swap (else, as keys are discarded on reboot,
> savecore(8) wouldn't have any way to
oops. Not 1 GB as I would have noticed it immediately because of
booting issues, but approaching 1 MB in size.
Thanks and sorry for the noise
On Fri, Feb 3, 2017 at 8:27 AM, Amit Kulkarni wrote:
> Ouch. I have it so big, so I can tar-pit ads! It is approaching 1GB
> in
After rebooting the machine (now in ordinary softdep mode, and fsck did
its job), I tried to do "rm -rf /home/lost+found", and got "ffs_blkfree:
freeing free block".
Find photo of panic screen attached here, with indefinite storage:
http://picpaste.com/Crash-0Lj3JJ2r.jpg .
I'm not so
Reproduction script:
Boot your OpenBSD 6.0 MP machine which has /home mounted as softdep, and
do:
mount -o async,nosoftdep -u /home
mkdir /home/exploit; cd /home/exploit
tar xfz /YOUR/INSTALLER/DIR/base60.tgz
tar xfz /YOUR/INSTALLER/DIR/base60.tgz
Outcome: The kernel will go into panic
Hi,
I have a OpenBSD 6.0 GENERIC.MP system set up as follows:
* sd0 is a physical harddrive. It has a "b" partition for swap, and an
"a" partition for a softraid. The softraid is represented by sd1 .
* sd1 is the softraid. It has some UFS partitions (a, d, etc.).
Importantly, it has no
On Thu, Feb 02, 2017 at 08:36:17PM -0600, Amit Kulkarni wrote:
> Hi,
>
> When I try to upgrade using bsd.rd, it fails like so (hand typed, so skipped
> the network config part to save keystrokes). I upgraded by following the old
> tar method listed in old releases.
>
> Available disks are: