On 3/9/11, Brett Lymn bl...@baea.com.au wrote:
On Wed, Mar 09, 2011 at 11:13:33PM -0700, Theo de Raadt wrote:
If you feel so strongly about it that you feel it to forward private
correspondence, then please leave our mailing lists.
Only following your lead.
Ah, so you feel that Theo's email
This is quite the entertaining thread.
Wish it was monday morning.
On Thu, 10 Mar 2011 16:53:07 +1030, Brett Lymn wrote:
On Wed, Mar 09, 2011 at 11:13:33PM -0700, Theo de Raadt wrote:
If you feel so strongly about it that you feel it to forward private
correspondence, then please leave our
I filed a bug report on this. PR 6577/system.
Thanks for the input, everyone.
Jeff Ross
Brett Lymn bl...@baea.com.au writes:
[...]
The safest way to do a dump is when the machine is in single user mode
for this very reason but many people play fast and loose because they
cannot wear the outage for a backup, in that case you must quiesce the
file systems as best you can.
On 2011-03-09 07.48, Brett Lymn wrote:
On Wed, Mar 09, 2011 at 01:49:04AM +0100, Benny Lofgren wrote:
I don't know about the rest of you guys, but to me that sounds exactly
like a bug... especially since nothing is mentioned of such behaviour in
the dump man page.
Well, you would have to
On 03/08/11 16:20, Brett Lymn wrote:
On Tue, Mar 08, 2011 at 02:50:19PM -0700, Jeff Ross wrote:
Is this worthy of a bug report or is there a peback afoot here?
Unlikely to be a bug more likely that you did a dump of a file system
that was changing while the dump was in progress. This
On 2011-03-09 16.28, Jeff Ross wrote:
The only way I found out of this loop is to ctrl-c.
That's the bug I'm asking about, but if what you write above is correct
my belief that dump is an adequate backup is now in question. No where
in the dump man page does it say that and that certainly
On Wed, Mar 09, 2011 at 06:54:07PM +0100, Benny Lofgren wrote:
I don't think the problem is so much with dump as it is with restore,
and even there it's likely not more than a nuisance for the operator.
Don't gamble any important data solely on that opinion, though...
When I have seen this
On Wed, Mar 09, 2011 at 08:28:31AM -0700, Jeff Ross wrote:
On 03/08/11 16:20, Brett Lymn wrote:
Unlikely to be a bug more likely that you did a dump of a file system
that was changing while the dump was in progress. This breaks the
backup and produces the sort of symptoms you are seeing
On Wed, Mar 09, 2011 at 10:47:54PM -0700, Theo de Raadt wrote:
Instead of helping a person who might have found a bug, I think you
are talking out of your ass.
If you say so Theo. Oddly, I have experienced exactly those systems
with backups from an file system that was being actively changed
On Thu, Mar 10, 2011 at 04:25:50PM +1030, Brett Lymn wrote:
On Wed, Mar 09, 2011 at 10:47:54PM -0700, Theo de Raadt wrote:
Instead of helping a person who might have found a bug, I think you
are talking out of your ass.
If you say so Theo. Oddly, I have experienced exactly those
On Wed, Mar 09, 2011 at 10:59:45PM -0700, Theo de Raadt wrote:
And when you did, did not file a bug report.
Not on OpenBSD.
And you did work on a patch.
Not on OpenBSD
So you suck.
I am sure both myself and Jeff will be thrilled when you find the bug.
thanks.
You are a
If you feel so strongly about it that you feel it to forward private
correspondence, then please leave our mailing lists.
I am sure others will feel the same; those of you who do, feel free
to explain the concept to him.
I still think you are a loser. If you have endured a real bug for
a long
On Wed, Mar 09, 2011 at 11:13:33PM -0700, Theo de Raadt wrote:
If you feel so strongly about it that you feel it to forward private
correspondence, then please leave our mailing lists.
Only following your lead.
I am sure others will feel the same; those of you who do, feel free
to explain
On OpenBSD -current (although this has happened before).
While restoring from file today I ran across this. At this point I've
already done the level 0 and level 1 restore.
root@slony:/var/www $ restore -i -f /backup/2.var_www
restore add *
restore: ./logs: File exists
restore: ./wykids:
On Tue, Mar 08, 2011 at 02:50:19PM -0700, Jeff Ross wrote:
Is this worthy of a bug report or is there a peback afoot here?
Unlikely to be a bug more likely that you did a dump of a file system
that was changing while the dump was in progress. This breaks the
backup and produces the sort of
On 2011-03-09 00.20, Brett Lymn wrote:
On Tue, Mar 08, 2011 at 02:50:19PM -0700, Jeff Ross wrote:
Is this worthy of a bug report or is there a peback afoot here?
Unlikely to be a bug more likely that you did a dump of a file system
that was changing while the dump was in progress. This breaks
On Wed, Mar 09, 2011 at 01:49:04AM +0100, Benny Lofgren wrote:
I don't know about the rest of you guys, but to me that sounds exactly
like a bug... especially since nothing is mentioned of such behaviour in
the dump man page.
Well, you would have to totally redo the guts of dump if you
18 matches
Mail list logo
