LVM on two disks - spin down?
Hi all, If I have a LVM which uses two partitions on two different disks and at least one of its subvolumes is always in use, can the second disk spin down? An example showing what I mean: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |/dev/sda1 ||/dev/sdb1 | |_ _ _ _ _ _ _ _||_ _ _ _ _ _ _ _| lvmGrp = /dev/sda1 + /dev/sdb1 _ _ _ _ _ _ _ _ _ _ _ _ _ |lvm1 | |lvm2 ||lvm3 | |_ _ _ _| |_ _ _||_ _ _ _ _ _| So since sdb is new, if I add lvm3 it will be on sdb1 and not sda1, correct?; if I don't mount lvm3 automatically, can sdb spin down although lvm1 and lvm2 are used? The reason for this setup is the possibility to extend e.g. lvm2 later with space on sdb1 if it is really required without any re-formatting. (Of course I will loose the spin down then, but for the time being I'd take care of my new disk.) Thanks in advance... signature.asc Description: This is a digitally signed message part.
Re: Partitioning of new machine - thank you
On Saturday 09 August 2014 11.11:08 Gary Dale wrote: > > To preserve your archive, I'd advise PAR2 redundancy files to fix any > problems that may crop up. So long as your HD copies are good, you don't > need to go to the PAR2 files, but should one develop a problem, you can > fix it with the PAR2 files. Having 5% to 10% redundancy is a lot cheaper > than RAID1. > > You can automate the PAR2 creation by checking for new files and > creating PAR2s for them. Thank you all for the great ideas and opinions. I've decided to use only one internal ext4 partition w/o any RAID for the photos together with par2 for the anti-bit rot plus the external backup. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/7613649.RF3m1Bm1Vz@yucca
High %wa, irregular blocking
Hi, Some weeks ago I installed Testing on my wife's iMac [1] from 2008. Unfortunately it has one issue: There are irregular periods of very high %wa, maybe 3-5 times per hour, not directly related to a certain user action. They last for some seconds up to even a minute or so and render the machine unusable for that time. top shows %wa of 80 or 90%, load can go up to 9 on this dual core machine, iotop shows only a few KB/s. I already added pcie_aspm=off to the boot options which seems to help, but I still see this I/O hangs (without, I had about 10+ hangs per hour). Any idea what could cause these blockings? How can I find out more? I use Linux for 15+ years but I never saw such things... and I want to show my wife, that Linux is the better OS, of course... ;-) Aside from that issue everything runs quite nicely. Thanks & best regards, Bernd [1] iMac 8,1: 2008, Core 2 Duo 2.8 GHz, GB RAM, 500 GB WD HDD, ATI Radeon HD 2600 PRO (PCIe) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/795b1b69-6831-4ee7-9988-fa0ef6132...@gmx.ch
Re: High %wa, irregular blocking
> Hi
>
> On Wed, Jun 04, 2014 at 08:49:44AM +0200, b-m...@gmx.ch wrote:
> > Hi,
> >
> > Some weeks ago I installed Testing on my wife's iMac [1] from 2008.
> > Unfortunately it has one issue:
> >
> > There are irregular periods of very high %wa, maybe 3-5 times per hour,
> > not
> > directly related to a certain user action. They last for some seconds up
> > to
> > even a minute or so and render the machine unusable for that time. top
> > shows %wa of 80 or 90%, load can go up to 9 on this dual core machine,
> > iotop shows only a few KB/s.
>
> High wait-for-IO combined with very little disk throughput usually
> points towards disk problems...
>
> Anything interesting from e.g. "iostat -kNx" ? That should tell you
> which disk and partition is suffering. (Or if you already think you
> know, this should confirm it)
Well, I already had a look at hdparm, but everything looks ok.
Booting OSX there are no similar problems, so a cable problem doesn't seem to
be the case.
I will have a look at iostat when there are huge hangs again (I'm a bit in a
hurry now...)
>
> > I already added pcie_aspm=off to the boot options which seems to help,
> > but I still see this I/O hangs (without, I had about 10+ hangs per hour).
> >
> > Any idea what could cause these blockings? How can I find out more? I use
> > Linux for 15+ years but I never saw such things... and I want to show my
> > wife, that Linux is the better OS, of course... ;-)
>
> My first call would be the kernel logs. IIRC in the default syslog
> config this goes to /var/log/kern.log, but you can see the most recent
> output with e.g. "dmesg" or "dmesg -T"
$ grep ata kern.log:
Jun 5 19:50:02 Yucca kernel: [0.00] BIOS-e820: [mem
0xbfec5000-0xbfec7fff] ACPI data
Jun 5 19:50:02 Yucca kernel: [0.00] BIOS-e820: [mem
0xbfedf000-0xbfeeefff] ACPI data
Jun 5 19:50:02 Yucca kernel: [0.00] ACPI: SSDT bfedf000 000137
(v01 APPLE SataAhci 1000 INTL 20061109)
Jun 5 19:50:02 Yucca kernel: [0.00] Memory: 3962208K/4190296K
available (4811K kernel code, 693K rwdata, 1596K rodata, 984K init, 952K bss,
228088K reserved)
Jun 5 19:50:02 Yucca kernel: [0.088000] perf_event_intel: PEBS disabled
due to CPU errata
Jun 5 19:50:02 Yucca kernel: [0.179283] ACPI : EC: GPE = 0x17, I/O:
command/status = 0x66, data = 0x62
Jun 5 19:50:02 Yucca kernel: [1.641833] Write protecting the kernel
read-only data: 8192k
Jun 5 19:50:02 Yucca kernel: [1.70] libata version 3.00 loaded.
Jun 5 19:50:02 Yucca kernel: [1.800870] ata1: SATA max UDMA/133 abar
m2048@0xd0704000 port 0xd0704100 irq 46
Jun 5 19:50:02 Yucca kernel: [1.800872] ata2: DUMMY
Jun 5 19:50:02 Yucca kernel: [1.800874] ata3: DUMMY
Jun 5 19:50:02 Yucca kernel: [1.800918] ata_piix :00:1f.1: version 2.13
Jun 5 19:50:02 Yucca kernel: [1.802216] scsi3 : ata_piix
Jun 5 19:50:02 Yucca kernel: [1.802263] scsi4 : ata_piix
Jun 5 19:50:02 Yucca kernel: [1.802292] ata4: PATA max UDMA/100 cmd 0x4108
ctl 0x411c bmdma 0x40e0 irq 21
Jun 5 19:50:02 Yucca kernel: [1.802293] ata5: PATA max UDMA/100 cmd 0x4100
ctl 0x4118 bmdma 0x40e8 irq 21
Jun 5 19:50:02 Yucca kernel: [1.967781] ata4.00: ATAPI: MATSHITADVD-R
UJ-875, DB09, max UDMA/66
Jun 5 19:50:02 Yucca kernel: [1.980376] ata4.00: configured for UDMA/66
Jun 5 19:50:02 Yucca kernel: [2.120029] ata1: SATA link up 3.0 Gbps
(SStatus 123 SControl 300)
Jun 5 19:50:02 Yucca kernel: [2.120893] ata1.00: ACPI cmd
ef/90:03:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
Jun 5 19:50:02 Yucca kernel: [2.158384] ata1.00: ATA-8: WDC
WD5000AAKS-40YGA0, 58.01E02, max UDMA/133
Jun 5 19:50:02 Yucca kernel: [2.158387] ata1.00: 976773168 sectors, multi
0: LBA48 NCQ (depth 31/32), AA
Jun 5 19:50:02 Yucca kernel: [2.159267] ata1.00: ACPI cmd
ef/90:03:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
Jun 5 19:50:02 Yucca kernel: [2.159469] ata1.00: configured for UDMA/133
Sometimes there are also several/many lines like:
May 20 18:50:09 XXX kernel: [ 1542.816063] ata1.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x6 frozen
May 20 18:50:09 XXX kernel: [ 1542.816073] ata1.00: failed command: READ DMA EXT
May 20 18:50:09 XXX kernel: [ 1542.816083] ata1.00: cmd
25/00:00:40:bc:cd/00:02:1d:00:00/e0 tag 0 dma 262144 in
May 20 18:50:09 XXX kernel: [ 1542.816083] res
40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
May 20 18:50:09 XXX kernel: [ 1542.816088] ata1.00: status: { DRDY }
May 20 18:50:09 XXX kernel: [ 1542.816095] ata1: hard resetting link
May 20 18:50:09 XXX kernel: [ 1543.136059] ata1: SATA link up 3.0 Gbps (SStatus
123 SControl 300)
May 20 18:50:09 XXX kernel: [ 1543.136992] ata1.00: ACPI cmd
ef/90:03:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04)
May 20 18:50:10 XXX kernel: [ 1543.168706] ata1.00: ACPI cmd
ef/90:03:00:00:00:a
Iceweasel and kprinter4
Hi all, Does anybody know how to configure Iceweasel to use the KDE printer dialog - I found instructions on the net but they seem to be quite outdated and don't work anymore. Thanks a lot. signature.asc Description: This is a digitally signed message part.
scanbd
Hi list, I've set up scanbd successfully on my Jessie box (everything up to date, using systemd). Everything works really well if I start scanbd as user root on the command line, it scans for local-only device and finds my scanner which is connected via USB 3. If I start scanbd as a service it scans for the scanner... and finds nothing. Why? Where can I look? A permission problem? But it's the same configuration, once started as root, once as a service. From scanbd.conf: [...] user = saned group = scanner [...] Thanks for any hints. Bernd signature.asc Description: This is a digitally signed message part.
Strange problem with *.local / avahi / zeroconf
Hi list, I've a very strange problem in my home network: One machine runs apache2 with services like owncloud as well as avahi-daemon. Other machines (clients) connect to it, e.g. with the owncloud client, using .local as URL. After some time, maybe 2 or 3 minutes or so, the other machines loose the connection. In a browser I cannot connect, I cannot ping, nothing. It's absolute reproducable. If I restart a client, it can reconnect, but only for a few minutes. This happens for both, Jessie and Mac OS clients. I went already through a reset of the router, no effect. How can I find the cause of this problem? Thanks a lot for any help! B. signature.asc Description: This is a digitally signed message part.
Re: Strange problem with *.local / avahi / zeroconf
On Friday 29 May 2015 18.11:29 Arno Schuring wrote: > Hi=2C > > > One machine runs apache2 with services like owncloud as well as avahi-dae= > > mon.=20 > > > Other machines (clients) connect to it=2C e.g. with the owncloud client= > > =2C using=20 > > > .local as URL. > > > >=20 > > > > After some time=2C maybe 2 or 3 minutes or so=2C the other machines loose= > > the=20 > > > connection. In a browser I cannot connect=2C I cannot ping=2C nothing. It= > > 's=20 > > > absolute reproducable. > > You cannot ping the machine's ip address=2C or you cannot reach (resolve) t= > he > .local hostname? > > >=20 > > > > If I restart a client=2C it can reconnect=2C but only for a few minutes. = > > This=20 > > > happens for both=2C Jessie and Mac OS clients. > > > >=20 > > > > I went already through a reset of the router=2C no effect. > > Your router has nothing to do with it=2C unless it's actively blocking the = > traffic. > The .local hostnames are resolved through mdns (multicast dns)=2C which > is provided by avahi-daemon on the server side=2C and libnss-mdns on the cl= > ient. > > You could use a tool like mdns-scan or avahi-discover to list the services = > on > the current network=2C to verify the presence or absence of the service. Sorry, forgot to mention, ping with ip does work, only ping with hostname.local doesn't. Avahi-discover is great, thanks! But I'm only one step further, since now after a reboot, when everything works as expected, it shows the server's hostname as a Workstation. I can get its details (IP address etc.) When connections using the hostname stopped working, the hostname is still shown as a Workstation, but I cannot get its details anymore, instead I get the following error: org.freedesktop.Avahi.TimeoutError: Timeout reached What timeout is that, one on the server or one on the client? I still don't get it :-( Thanks! B. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/6052427.A6P91jyklW@engiadina
