search for: thaws

On 13.09.2014 07:02, poma wrote: > On 13.09.2014 06:57, poma wrote: >> >> Actually I have nothing to show cause logs are all OK. >> Haha, it seems to me that the bugs become intelligent. >> >> 3.15.10-201.fc20.x86_64 >> 3.16.2-200.fc20.x86_64 >> 3.17.0-0.rc4.git3.2.fc22.1.x86_64 >> nouveau [ DRM] suspending display... >> nouveau [

...S2_OSB_FREEZE_INPROG); + return; + } + + spin_lock(&osb->osb_lock); + osb->osb_flags &= ~OCFS2_OSB_FREEZE_INPROG; + osb->osb_flags |= OCFS2_OSB_FROZEN_BY_REMOTE; + spin_unlock(&osb->osb_lock); + + ocfs2_wake_downconvert_thread(osb); + + /* Waits for thaw */ +wait_thaw: + /* thaws the fs if unmount is in progress. */ + ret = ocfs2_test_osb_flag(osb, OCFS2_OSB_UMOUNT_INPROG); + if (ret) { + /* Leave FREEZE_INPROG there so not queue the worker again */ + goto thaw_dev; + + } + + ret = ocfs2_freeze_lock_timeout(osb, 0, 50); + if (ret == -EBUSY) { + /* We suppose when it retu...

On Sat, Sep 13, 2014 at 4:52 PM, poma <pomidorabelisima at gmail.com> wrote: > On 13.09.2014 07:02, poma wrote: >> On 13.09.2014 06:57, poma wrote: >>> >>> Actually I have nothing to show cause logs are all OK. >>> Haha, it seems to me that the bugs become intelligent. >>> >>> 3.15.10-201.fc20.x86_64 >>> 3.16.2-200.fc20.x86_64

On Sat, Sep 13, 2014 at 5:25 PM, poma <pomidorabelisima at gmail.com> wrote: > On 13.09.2014 22:58, Ilia Mirkin wrote: >> On Sat, Sep 13, 2014 at 4:52 PM, poma <pomidorabelisima at gmail.com> wrote: >>> On 13.09.2014 07:02, poma wrote: >>>> On 13.09.2014 06:57, poma wrote: >>>>> >>>>> Actually I have nothing to show cause logs

Hello list, I've put CentOS 6.3 x86_64 on my desktop, replacing Fedora 17 x86_64. This is the first time I'm using CentOS on a desktop, so far only on the servers. The problem is with thawing from hibernation. Time from turning on the hibernated machine to reaching the login prompt is not that of an issue, although sometimes it can take a while (significantly more than with Fedora).

Dear Poma, Don't get anyone wrong, your input is greatly valued. The reason why "we" (nouveau developers) generally ask for a git bisection is because we don't know or track specific distributions. Although your search has narrowed the problem down (thanks for that!), we don't know how big the difference is between kernel-3.16.0-0.rc0.git9.1.fc21 and

On Wed, Aug 6, 2014 at 12:27 PM, Eric Blake <eblake@redhat.com> wrote: > On 08/06/2014 10:06 AM, Yuanzhen Gu wrote: > > yes, I got your point, thanks very much Eric. > > not entirely, because you still top-posted. > > got it entirely this time, not top-posted. > > > > If I want to take a distributed snapshot, which need pause all the VMs > and >

Hello, Turns out S3 is not different from S4 for virtio devices: the device is assumed to be reset, so the host and guest state are to be assumed to be out of sync upon resume. We handle the S4 case with exactly the same scenario, so just point the suspend/resume routines to the freeze/restore ones. Once that is done, we also use the PM API's macro to initialise the sleep functions. A

Hello, Turns out S3 is not different from S4 for virtio devices: the device is assumed to be reset, so the host and guest state are to be assumed to be out of sync upon resume. We handle the S4 case with exactly the same scenario, so just point the suspend/resume routines to the freeze/restore ones. Once that is done, we also use the PM API's macro to initialise the sleep functions. A

yes, I got your point, thanks very much Eric. If I want to take a distributed snapshot, which need pause all the VMs and then take snapshot, how can I control the pause for all the VMs? Is there only way that I turn to freeze/thaw functions? and freeze/thaw only for file systems, not for the whole guest, am I right? Thanks a lot! Best, Yuanzhen On Wed, Aug 6, 2014 at 11:35 AM, Eric Blake

Hi Peter, Should I assume that the virsh domfsfreeze, does not require the qemu-agent service in the guest? PS. I couldn't find the result. Afaik it looks like it is returning the amount of frozen/thawed filesystem's -----Original Message----- Cc: libvirt-users Subject: Re: guest-fsfreeze-freeze freezes all mounted block devices On Fri, Feb 14, 2020 at 22:14:55 +0100, Marc Roos

Hello all, I've some CTDB issue which I'm not sure where to start... I follow this guide by steve which is nice. The different on what have is that I don't have drbd running... Also I've 4 x GE which is all Connected to a switch with different ip but same subnet This is suppose to load balance the traffic as under samba dns, they all have the same name. I'm only planing 3

Use PM_FREEZE, PM_THAW and PM_RESTORE power events for suspend/resume/checkpoint functionality, instead of PM_SUSPEND and PM_RESUME. Use of these pm events fixes the Xen Guest hangup when taking checkpoints. When a suspend event is cancelled (while taking checkpoints once/continuously), we use PM_THAW instead of PM_RESUME. PM_RESTORE is used when suspend is not cancelled. See

Il 17/09/2018 22:12, Gordon Messmer ha scritto: > On 9/17/18 7:50 AM, Alessandro Baggi wrote: >> Running a backup I follow this steps: >> >> 1) Stop httpd >> 2) Create lvm snapshot on the dataset >> 3) Backup database >> 4) restart httpd (to avoid more downtime) >> 5) mount the snapshot and execute backup >> 6) umount and remove the snapshot

Il 18/09/2018 17:14, Gordon Messmer ha scritto: > On 9/17/18 11:38 PM, Alessandro Baggi wrote: >> Il 17/09/2018 22:12, Gordon Messmer ha scritto: >>> That doesn't look right.? It should look more like 1) stop or freeze >>> all of the services (httpd and database), 2) make the snapshot, 3) >>> start or thaw all of the services, 4) mount the snapshot, 5)

https://bugs.freedesktop.org/show_bug.cgi?id=94324 Bug ID: 94324 Summary: Nouveau driver breaks thaw (resume form hibernation) Product: xorg Version: 7.7 (2012.06) Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau

changes from v1 1): fs locking prototol version up 0.1 instead of change in dlm protocol version. 2): fixes the racing with umount. yet relies on cancelable cluster lock. 3): timeout the joinning in a cluster when it's frozen instead of waiting until thaw. yet relies on cancelable cluster lock. 4): fix deadlock(with super lock) when joining in a frozen cluster. Move freeze lock out of

I'd like to sum a matrix only where the matrix meets a specific condition. The matrix has 365 rows and about 50,000 columns. str(cdem.mat.yr) num [1:365, 1:41772] -43.5 -48.4 -45.9 -38.4 -32 ... I'm having trouble replicating this because it is not working out for me, so I'm unsure I can provide an solid working example (apologies). I would like to subset my matrix where the values

On 13.09.2014 22:58, Ilia Mirkin wrote: > On Sat, Sep 13, 2014 at 4:52 PM, poma <pomidorabelisima at gmail.com> wrote: >> On 13.09.2014 07:02, poma wrote: >>> On 13.09.2014 06:57, poma wrote: >>>> >>>> Actually I have nothing to show cause logs are all OK. >>>> Haha, it seems to me that the bugs become intelligent. >>>>

hi... i intend to develop a backup application for linux platform... the workflow is as follows: - freeze the file-system(ext2 or ext3) - take the bckup - release the file system. i am not able to find the relevant ioctl or api for freezing & releasing the file system... so... i need some help... thanks... Satish Singhal __________________________________________________ Do You Yahoo!?