search for: devive

...stems -- see other thread) is currently hung. I can ping it, but can't do much of anything else. When I switch to one of the virtual consoles, I can briefly see the "login:" prompt, but then that window immediately fills with up with the following message: EXT3-fs error (devive dm-0) in start_transaaction: Journal has aborted This is displayed over and over again. I used the default (automatic) partitioning scheme, so the root file system is an ext3 partition on a logical volume that spans most of the disk (everything except for the swap partition and /boot). A...

Hi, Alfred von Campe wrote on Wed, 2 Aug 2006 09:34:06 -0400 > It's time to resurrect this thread from way back in June. I suspect this is more of a HW problem rathan a SW one. About two years ago I had a similar EXT3 fs failure case to develop on a server running Mandrake Linux. My case was due to the fact that this desktop Linux computer had two HDs, where one of them (a Quamtum, top

...oot 89 Jul 31 21:54 tinc-up -rw-r--r-- 1 root root 83 Aug 1 10:43 tinc.conf # cat /etc/tinc/ffnw/tinc-up #!/bin/sh cd /etc/tinc/ffnw/hosts git pull ifconfig 10.0.1.10 netmask 255.255.255.0 # cat /etc/tinc/ffnw/tinc.conf Name = tinc_FF_OS_Lagerhalle_Offloader Devive = /dev/net/tun ConnectTo = master # cat /etc/tinc/ffnw/hosts/tinc_FF_OS_Lagerhalle_Offloader Subnet = 10.0.1.10 -----BEGIN RSA PUBLIC KEY----- <...> -----END RSA PUBLIC KEY----- # tincd -n ffnw -d5; logread | grep tinc Tue Aug 1 11:06:34 2017 daemon.notice tinc.ffnw[13461]: tincd 1.0....

This is very strange. Everything was running fine Friday night. This morning I walk into work and find that my root file system (which is actually the only filesystem besides /boot) is not writable. Yet mount thinks it's mounted read/write: # mount /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) [snip] # touch foo touch: cannot touch `foo': Read-only file

...mespace. The mails won't be counted in quota, # and they're not deleted automatically (use a cronjob or something). #lazy_expunge = .EXPUNGED/ .DELETED/ .DELETED/.EXPUNGED/ } and postfix as LDA: ... mailbox_command = /usr/lib/dovecot/deliver ... There are much logentrys about dovecot, devivering and mail, but no sieve- entrys in any log. Hope you can help me, Greets, Christoph PS the system: fritz!box (mipsel-cpu) debian etch (and backports; lenny + dovecot does not run with this environment) dovecot and postfix from etch-backports -- GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427...

This is an issue that I have been having with one of our production servers for a couple of months, just out of no where /var goes to read only. There aren't any errors that show up in /var/log/messages nor dmesg, I checked to make sure that the drives on error option is set to continue and there isn't anything as far as I can tell wrong with the disks. Also there is plenty of disk space.

...;t really add a > netdevice and enslave an existing one without a risk of breaking some > userspace configs. > I still don't understand this concern. Like said, before this patch becomes reality, users interact with raw VF interface all the time. Now this patch introduces a virtio net devive and enslave the VF. Users have to interact with two interfaces - IP address and friends configured on the VF will get lost and users have to reconfigure virtio all over again. But some other configs e.g. ethtool needs to remain on the VF. How does it guarantee existing configs won't broken? App...

...etdevice and enslave an existing one without a risk of breaking some >> userspace configs. >> > I still don't understand this concern. Like said, before this patch > becomes reality, users interact with raw VF interface all the time. > Now this patch introduces a virtio net devive and enslave the VF. > Users have to interact with two interfaces - IP address and friends > configured on the VF will get lost and users have to reconfigure > virtio all over again. But some other configs e.g. ethtool needs to > remain on the VF. How does it guarantee existing configs w...

...an existing one without a risk of breaking some >>> userspace configs. >>> >> I still don't understand this concern. Like said, before this patch >> becomes reality, users interact with raw VF interface all the time. >> Now this patch introduces a virtio net devive and enslave the VF. >> Users have to interact with two interfaces - IP address and friends >> configured on the VF will get lost and users have to reconfigure >> virtio all over again. But some other configs e.g. ethtool needs to >> remain on the VF. How does it guarantee ex...

On Mon, Jan 22, 2018 at 1:41 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > On Mon, Jan 22, 2018 at 12:27:14PM -0800, Siwei Liu wrote: >> First off, as mentioned in another thread, the model of stacking up >> virt-bond functionality over virtio seems a wrong direction to me. >> Essentially the migration process would need to carry over all guest >> side

On Mon, Jan 22, 2018 at 1:41 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > On Mon, Jan 22, 2018 at 12:27:14PM -0800, Siwei Liu wrote: >> First off, as mentioned in another thread, the model of stacking up >> virt-bond functionality over virtio seems a wrong direction to me. >> Essentially the migration process would need to carry over all guest >> side