Re: holding disk too small? -- holding disk RAID configuration

[Nathan Stratton Treadway]

On Tue, Dec 03, 2019 at 15:43:10 +0100, Stefan G. Weichinger wrote:
> I consider recreating that holding disk array (currently RAID1 of 2
> disks) as RAID0 ..

Just focusing on this one aspect of your question: assuming the
filesystem in question doesn't have anything other than the Amanda
holding-disk area on it, I suspect you would be better off creating two
separate filesystems, one on each underlying disk, rather than making
them into a RAID0 array.

Amanda can make use of two separate holding-disk directories in
parallel, so you can still get twice the total holding disk size
avilable in a run (compared to the current RAID1 setup), but Ananda's
parallel accesses will probably cause less contention on the physical
device since each filesystem is stored independently on one drive.


(Also, if one of the drives fails the other holding disk filesystem will
still be available, while if you are using RAID0 one drive failing will
take out the whole array)

Nathan


Nathan Stratton Treadway  -  natha...@ontko.com  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239

Re: holding disk too small?

[Stefan G. Weichinger]

Am 03.12.19 um 15:43 schrieb Stefan G. Weichinger:
> 
> Another naive question:
> 
> Does the holdingdisk have to be bigger than the size of one tape?

As there were multiple replies to my original posting and as I am way
too busy right now: a quick "thanks" to all the people who replied.

So far the setup works. Maybe not optimal, but it works.

;-)

stay tuned ...

Re: holding disk too small?

[Gene Heskett]

On Thursday 05 December 2019 10:50:34 Charles Curley wrote:
And I replied back on the list where this belongs, even if some of it is 
me blowing my own horn.

> On Thu, 5 Dec 2019 00:00:24 -0500
>
> Gene Heskett  wrote:
> > Lesson #2, I just learned today that the raspbian AND debian buster
> > 10.2 versions have NO inetd or xinetd. Ditto for RH.
>
> I don't know where you get that idea, as far as Debian goes.
>
That list is where I git that info, and it mention that RH was doing it 
too, so I checked my only buster install, which did not yet belong to my 
amanda setup and discovered both were missing on my rpi4/buster 10.2 
raspbian install.  But as you saw from my previous post this morning, 
apt now calls in some bsd stuff which I assume 
installs /etc/xinetd.d/amanda, which itself has a new option I've not 
seen before. It was not there before I had apt install the client stuff.

Because I had played with debians buster arm64 installs on both the pi3 
and the pi4, I know for a fact that touching those clients from the 
server, crashes the arm64 installs, leaving nothing in the logs.  I 
liked the idea of debians arm64 actually using grub to boot instead of 
the u-boot BS, but debian's amanda versions of the client stuff are 
instant crashers.  Between that and the relatively poor latency 
performance of the arm64 with its bigger stack frame, I reasoned that 
the armhf was the install of choice, raspbian was still on armhf, and 
its running beautifully, dead stable, moving that bigger lathe faster 
and sweeter than the pi3 ever did.  And building its own food on itself.  
The rpi4 has arrived IOW.  The only thing I'd do diff is order the 4GB 
model. A 2GB needs close to 3Gigs  of swap to build LinuxCNC, but it 
does it just fine. Swap is not on the u-sd card, but on a 120Gig SSD 
plugged into a sata<->usb3 adapter, making it much faster than spinning 
rust...

Since I'm just barely doing email on a machine pulled pulled out of the 
midden heap in the garage, and this boot drive is the boot drive I'll 
install in the new server when the rest of it arrives, I've not gone any 
further until the new system is up and running. With the realtime kernel 
pinned, uptime is now 13 days, and will probably run till the next power 
bump.

Anyway, thats the story and I'm sticking to it. You can download that 
bleeding edge rpi4 stuff from my web page, but as thats on this drive, 
in this temp machine, it will be watching paint dry slow and maybe die 
mid download as the OOM may kill it.

Time to go see what I'm fixing us for lunch.

 > root@jhegaala:~# cat /etc/debian_version
> 10.2
> root@jhegaala:~# apt-cache search inetd | grep inetd
> inetutils-inetd - internet super server
> libnl-idiag-3-200 - library for dealing with netlink sockets -
> inetdiag interface openbsd-inetd - OpenBSD Internet Superserver
> puppet-module-puppetlabs-xinetd - Puppet module for xinetd
> reconf-inetd - maintainer script for programmatic updates of
> inetd.conf rinetd - Internet TCP redirection server
> rlinetd - gruesomely over-featured inetd replacement
> update-inetd - inetd configuration file updater
> xinetd - replacement for inetd with many enhancements
> root@jhegaala:~#
>
> Indeed, amanda depends on openbsd-inetd:
>
> root@jhegaala:~# apt show amanda-common | grep inetd
>
> WARNING: apt does not have a stable CLI interface. Use with caution in
> scripts.
>
> Depends: adduser, bsd-mailx | mailx, debconf (>= 0.5) | debconf-2.0,
> openbsd-inetd | inet-superserver, update-inetd, perl (>= 5.28.0-3),
> perlapi-5.28.0, libc6 (>= 2.27), libcurl4 (>= 7.16.2), libglib2.0-0
> (>= 2.41.1), libssl1.1 (>= 1.1.0) root@jhegaala:~#
>
> I believe that we should remove the dependencies on openbsd-inetd |
> inet-superserver and update-inetd, and make those suggested, and
> encourage amanda over SSH, but that's another can of lawyers.



Copyright 2019 by Maurice E. Heskett
Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: holding disk too small?

[Charles Curley]

On Thu, 5 Dec 2019 04:43:15 -0500
Gene Heskett  wrote:

> > # systemctl status amanda.socket  
> pi@rpi4:/etc $ sudo systemctl status amanda.socket
> Unit amanda.socket could not be found.

Same on Debian 10.2. Also, it appears that no Debian 10.2 package
provides amanda.service:

charles@hawk:~$ apt-file search amanda.service
charles@hawk:~$ 

So I expect amanda.service is a Fedora-ism.


-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: holding disk too small?

[Charles Curley]

On Thu, 5 Dec 2019 00:00:24 -0500
Gene Heskett  wrote:

> Lesson #2, I just learned today that the raspbian AND debian buster
> 10.2 versions have NO inetd or xinetd. Ditto for RH.

I don't know where you get that idea, as far as Debian goes.

root@jhegaala:~# cat /etc/debian_version 
10.2
root@jhegaala:~# apt-cache search inetd | grep inetd
inetutils-inetd - internet super server
libnl-idiag-3-200 - library for dealing with netlink sockets - inetdiag 
interface
openbsd-inetd - OpenBSD Internet Superserver
puppet-module-puppetlabs-xinetd - Puppet module for xinetd
reconf-inetd - maintainer script for programmatic updates of inetd.conf
rinetd - Internet TCP redirection server
rlinetd - gruesomely over-featured inetd replacement
update-inetd - inetd configuration file updater
xinetd - replacement for inetd with many enhancements
root@jhegaala:~# 

Indeed, amanda depends on openbsd-inetd:

root@jhegaala:~# apt show amanda-common | grep inetd

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Depends: adduser, bsd-mailx | mailx, debconf (>= 0.5) | debconf-2.0, 
openbsd-inetd | inet-superserver, update-inetd, perl (>= 5.28.0-3), 
perlapi-5.28.0, libc6 (>= 2.27), libcurl4 (>= 7.16.2), libglib2.0-0 (>= 
2.41.1), libssl1.1 (>= 1.1.0)
root@jhegaala:~# 

I believe that we should remove the dependencies on openbsd-inetd |
inet-superserver and update-inetd, and make those suggested, and
encourage amanda over SSH, but that's another can of lawyers.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: holding disk too small?

[Gene Heskett]

On Thursday 05 December 2019 02:12:52 Uwe Menges wrote:

> On 2019-12-05 06:00, Gene Heskett wrote:
> > Lesson #2, I just learned today that the raspbian AND debian buster
> > 10.2 versions have NO inetd or xinetd. Ditto for RH.
>
> I think that's along with other stuff moving to systemd.
> On Fedora 30, I have
>
> # systemctl status amanda.socket
pi@rpi4:/etc $ sudo systemctl status amanda.socket
Unit amanda.socket could not be found.

> ● amanda.socket - Amanda Activation Socket
>Loaded: loaded (/usr/lib/systemd/system/amanda.socket; enabled;
> vendor preset: disabled)
>Active: active (listening) since Sat 2019-11-30 14:46:46 CET; 4
> days ago Listen: [::]:10080 (Stream)
>  Accepted: 0; Connected: 0;
> Tasks: 0 (limit: 4915)
>Memory: 0B
>CGroup: /system.slice/amanda.socket
>
> Nov 30 14:46:46 lima systemd[1]: Listening on Amanda Activation
> Socket.
>
> # systemctl cat amanda.socket
> # /usr/lib/systemd/system/amanda.socket
> [Unit]
> Description=Amanda Activation Socket
>
> [Socket]
> ListenStream=10080
> Accept=true
>
> [Install]
> WantedBy=sockets.target

So I had apt install the usual suspects since that did nothing to this 
machine.

>pi@rpi4:/etc $ sudo apt install amanda-common amanda-client
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  openbsd-inetd tcpd
Suggested packages:
  dump gnuplot smbclient
The following NEW packages will be installed:
  amanda-client amanda-common openbsd-inetd tcpd
0 upgraded, 4 newly installed, 0 to remove and 6 not upgraded.
Need to get 2,363 kB of archives.
After this operation, 9,161 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://mirror.pit.teraswitch.com/raspbian/raspbian buster/main 
armhf tcpd armhf 7.6.q-28 [21.5 kB]
Get:2 http://mirror.pit.teraswitch.com/raspbian/raspbian buster/main 
armhf openbsd-inetd armhf 0.20160825-4 [34.3 kB]
Get:3 http://mirror.pit.teraswitch.com/raspbian/raspbian buster/main 
armhf amanda-common armhf 1:3.5.1-2+b3 [1,889 kB]
Get:4 http://mirror.pit.teraswitch.com/raspbian/raspbian buster/main 
armhf amanda-client armhf 1:3.5.1-2+b3 [418 kB]
Fetched 2,363 kB in 3s (825 kB/s)
Preconfiguring packages ...
Selecting previously unselected package tcpd.
(Reading database ... 263218 files and directories currently installed.)
Preparing to unpack .../tcpd_7.6.q-28_armhf.deb ...
Unpacking tcpd (7.6.q-28) ...
Selecting previously unselected package openbsd-inetd.
Preparing to unpack .../openbsd-inetd_0.20160825-4_armhf.deb ...
Unpacking openbsd-inetd (0.20160825-4) ...
Selecting previously unselected package amanda-common.
Preparing to unpack .../amanda-common_1%3a3.5.1-2+b3_armhf.deb ...
Unpacking amanda-common (1:3.5.1-2+b3) ...
Selecting previously unselected package amanda-client.
Preparing to unpack .../amanda-client_1%3a3.5.1-2+b3_armhf.deb ...
Unpacking amanda-client (1:3.5.1-2+b3) ...
Setting up tcpd (7.6.q-28) ...
Setting up openbsd-inetd (0.20160825-4) ...
Created symlink /etc/systemd/system/multi-user.target.wants/inetd.service 
→ /lib/systemd/system/inetd.service.
Setting up amanda-common (1:3.5.1-2+b3) ...
backup:x:34:34:backup:/var/backups:/usr/sbin/nologin
Adding user `backup' to group `disk' ...
Adding user backup to group disk
Done.
Adding user `backup' to group `tape' ...
Adding user backup to group tape
Done.
Setting up amanda-client (1:3.5.1-2+b3) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for systemd (241-7~deb10u2+rpi1) ...

Looks good, but:

pi@rpi4:/etc $ sudo systemctl status amanda.socket
Unit amanda.socket could not be found.

Clearly, the install is incomplete.  Or is it?, there is now 
an /etc/xinetd.d/ with an amanda file that was not there before. And it 
has arguments I've not seen before:

service amanda
{
disable = no
flags   = IPv4
socket_type = stream
protocol= tcp
wait= no
user= backup
group   = disk
groups  = yes
server  = /usr/lib/amanda/amandad
server_args = -auth=bsdtcp amdump amindexd amidxtaped 
senddiscover
}

That last I've not seen before. And /etc/amandahosts looks incomplete.

The rest of the checking will have to wait till the new server is 
running. Tomorrow (Friday maybe). This one doesn't have the cajones to 
run amanda and kmail at the same time.


>
> Yours, Uwe

Looks like they've at least tried to fix it. But that will be quite a 
heavy load since it has two aux ssd drives attached that contain stuff 
no one else has done (yet).  There's a reason its called bleeding 
edge...  And I'll sure sleep better if its backed up.

Thanks Uwe.

Copyright 2019 by Maurice E. Heskett
Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect