Displaying 5 results from an estimated 5 matches similar to: "Big send/receive hangs on 2009.06"
2010 Mar 05
2
ZFS replication send/receive errors out
My full backup script errorred out the last two times I ran it. I''ve got
a full Bash trace of it, so I know exactly what was done.
There are a moderate number of snapshots on the zp1 pool, and I''m
intending to replicate the whole thing into the backup pool.
After housekeeping, I take make a current snapshot on the data pool (zp1).
Since this is a new full backup, I then
2009 Feb 22
11
Confused about zfs recv -d, apparently
First, it fails because the destination directory doesn''t exist. Then it
fails because it DOES exist. I really expected one of those to work. So,
what am I confused about now? (Running 2008.11)
# zpool import -R /backups/bup-ruin bup-ruin
# zfs send -R "zp1 at bup-20090222-054457UTC" | zfs receive -dv
bup-ruin/fsfs/zp1"
cannot receive: specified fs (bup-ruin/fsfs/zp1)
2009 Jan 30
1
Crash shortly after importing pool
Looks like my main data pool is borked. I''ve got one essentially current
backup, and one older backup, plus the photos are mostly backed up on
archival optical disks, so this isn''t as disastrous as it might be, but
still, recovering several hundred gigabytes on home equipment is a pain.
Hence I''d prefer to recover the pool if that''s reasonably possible.
When
2014 Sep 22
1
sieve redirect to foreign email gets “Relay access denied”
I have a postfix mail server with sql authentication and I want to
implement sieve on it.
Sieve is working relative good, rules who contain 'fileinto' are
executed perfectly.
The problem is the redirect to other servers.
I configured a rule in Sieve to redirect any email containing "redirect"
in subject to a specified foreign destination. #
So practically a email coming from
1997 Feb 05
0
bliss version 0.4.0
[mod: Forwarded by Jeff Uphoff. I tried to mangle the headers that
it appears as the original post: with an invalid return address. -- REW]
A few months back, a very alpha version of bliss got posted. That shouldn''t
have happened, but, it was pretty much ignored so I didn''t worry about it.
But now it seems there''s a bit of a fuss about this. I''ll post the