search for: orphaning

On Mon, Jan 22, 2018 at 05:24:44PM +0100, Achim Gottinger via samba wrote: > Am 22.01.2018 um 10:49 schrieb Stefan Metzmacher via samba: > > Also DO NOT repair the following errors with samba-tool dbcheck! > > "Remove duplicate links in attribute" > > and > > "ERROR: orphaned backlink" > > as this removes the ability to repair the database >

Hi btrfs-team/-users, I do observe a strange behavior upon booting of my openSUSE 12.1 system ( kernel 3.1.10-1.9-desktop; x86_64 ) with btrfsprogs-0.19-43.7.1.x86_64 utils installed: The system has two btrfs-vols: root(sda7) & home(sda8) and had been created during system setup of openSUSE 12.1: # btrfs filesystem show Label: none uuid: a288fcff-28c8-4764-8efe-1e0cb205d588

Hello last week we updated three domain controllers (Sernet Samba) from 4.2 to 4.7, typical upgrade path (4.3->4.4->4.5->4.6->4.7), everything was ok. The next day we got a mail from the Sernet team informing they fixed a bug affecting the group memberships. https://bugzilla.samba.org/show_bug.cgi?id=13095 We've applied the update and few days after the update which should

Hello, last fsck says my /tmp and my /home files system has errors, here is the log from fsck using the read-only option: How to recover from this savely? How to avoid this in future? i am using kernel 2.4.18 with the acl-patches from acl.bestbits.at and the patches for the fileutils and e2fsprogs. If you need more informations please mail.

Stephen, OK, I can now reproduce this hang at will, purely by pulling the plug on my desktop when logged in and then rebooting - its a gnome desktop box with few partitions and ext3 on all of them, so I guess its getting a pile of gnome or ssh related sockets kept in /tmp which is on root To recap, when the machine is suffering from this, it hangs at the point of mounting the root filesystem

Hello, last fsck says my /tmp and my /home files system has errors, here is the log from fsck using the read-only option: How to recover from this savely? How to avoid this in future? i am using kernel 2.4.18 with the acl-patches from acl.bestbits.at and the patches for the fileutils and e2fsprogs. If you need more informations please mail.

Hi Samba team and Maxence, > last week we updated three domain controllers (Sernet Samba) from 4.2 to > 4.7, typical upgrade path (4.3->4.4->4.5->4.6->4.7), everything was ok. > > The next day we got a mail from the Sernet team informing they fixed a > bug affecting the group memberships. > > https://bugzilla.samba.org/show_bug.cgi?id=13095 > > We've

Because orphan cleanup now happens well after the fs is all initialized and such, we can run into this problem where we find orphan entries that were just added to the fs, not ones that were added previously during a crash. This does not bode well for the system, and results in a couple of odd things happening, like truncate being run on non-regular files. In order to fix this we just check and

Srini, Ok, you can go ahead and cook up the background orphan cleaner. Now, we can do this in a workqueue, a thread, or a timer. I don't see why a timer doesn't work. When the timer fires, you do this: 1. Take EX on a new orphan_scan lock. 2. check the LVB for the last scan time. If it's less than the scan timeout, reset the timer for (timeout - last scan), drop the EX, and

Currently we only queue recovery during mount if the journal is dirty. If the last node holding orphans in other node's orphan directory dies and is the first one to mount then it only recovers its orphan directory which leaves the orphans in other nodes slots. Since the other nodes journals are clean they will not queue to recover their orphan directory. This patch queues to recover orphans

I booted the guest in which i was testing btrfs (transient ENOSPC issues, etc). It booted in emergency mode. [ 6.705187] device label testfs1 devid 1 transid 4141 /dev/sdb1 [ 6.724353] device label fedora devid 1 transid 2036 /dev/sda2 [ 6.780931] device label fedora devid 1 transid 2036 /dev/sda2 [ 6.817157] snd_hda_intel 0000:00:04.0: irq 42 for MSI/MSI-X [ 6.818326]

Is there a reason why an ext3 root partition cannot be copied to an alternate partition using the "dd" command? The dd is copying the mounted root partition into an alternate partition that is not mounted. The dd returns success, but the fsck on that partition fails with errors as follows: ----------------- fsck 1.37 (21-Mar-2005) /dev/Active_Update/root2: recovering journal

Hi Joel/Srini, Here are 2 patches for orphan lock in local mode. patch 1: In local mode, we don't need lvb, so don't init it. patch 2: In local mode, orphan lock and unlock don't need to go to dlm part. Regards, Tao

Dear R-Devel subscriber, I would like to raise a topic and ask for your advice, guidance. Today on R-help an issue with a certain package popped up that has been removed from CRAN, because it failed the checks and/or the dependencies are not any longer available. The package maintainer has been alerted to this issue a couple of times and kindly asked to fix the code, such that it fullfills the

Are there many packages that are orphaned, and have a better "half" much like bootstrap? Is there a listing, or directory of "recommended" packages (other than the packages downloaded with the initial R install)? Thanks, Neil Eastep. An "R" newbie ----------- Prof Brian Ripley <ripley at stats.ox.ac.uk> writes: >>Package bootstrap is orphaned, that

I tried to join a samba4 to a win2008r2 level domain (OS level 2012) running exchange 2010. The join succeeds but the later replication is broken due to schema differences. In order to to find the cause, I started a test setup with: * a win2008r2 DC w/ minimal AD * upgraded the schema and the OS to 2012 (function level is still 2008r2) * and added a exchange server to the domain. And that is

The CRAN policy page (https://cran.r-project.org/web/packages/policies.html) implies that there is a formal procedure for orphaning a package but none is mentioned in the Extensions manual (https://cran.r-project.org/doc/manuals/r-devel/R-exts.html). This page (https://cran.r-project.org/src/contrib/Orphaned/README) implies that one would simply resubmit the package to CRAN with the text "ORPHANED" in the `Maintainer...

We''ve been seeing warnings coming out of the orphan commit stuff forever from ceph. Turns out it''s because we''re racing with checking if the orphan block reserve is set, because we clear it outside of the spin_lock. So leave the normal fastpath checks where they are, but take the spin_lock and _recheck_ to make sure we haven''t had an orphan block rsv added in

In fixing how we deal with bad inodes, we had a regression in the orphan cleanup code, since it expects to get a bad inode back. So fix it to deal with getting -ESTALE back by deleting the orphan item manually and moving on. Thanks, Reported-by: Simon Kirby <sim@hostway.ca> Signed-off-by: Josef Bacik <josef@redhat.com> --- fs/btrfs/inode.c | 36

I noticed while running xfstests 83 that if we didn''t have enough space to delete our inode the orphan cleanup would just loop. This is because it keeps finding the same orphan item and keeps trying to kill it but can''t because we don''t get an error back from iput for deleting the inode. So keep track of the last guy we tried to kill, if it''s the same as the