similar to: Case: package removed from CRAN, but not orphaned

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, yesterday I experienced following problem with my ext3 filesystem: - I had ext3 filesystem of the size of a few TB with journal. I correctly unmounted it and it was marked clean. - I then ran fsck.etx3 -f on it and it did not find any problem. - After increasing size of its LVM volume by 1.5 TB I resized the filesystem by resize2fs lvm_volume and it finished without problem. - But

As the list of packages on CRAN becomes longer almost on a weekly basis, we need a formal mechanism to handle the case when somebody wants to resign from maintaining a package. Possible reasons for orphanizing a package: 1) The current maintainer actively wants to orphanize the package, e.g., because he has no longer the time or interest to act as package maintainer. 2) The current

As the list of packages on CRAN becomes longer almost on a weekly basis, we need a formal mechanism to handle the case when somebody wants to resign from maintaining a package. Possible reasons for orphanizing a package: 1) The current maintainer actively wants to orphanize the package, e.g., because he has no longer the time or interest to act as package maintainer. 2) The current

Is there a list of commands for cleaning up orphaned DC's. I used ntdsutil on the Windows boxes no problem. Used an LDAP gui tool to remove the LDAP entries. Sadly Samba4 is still trying to contact the orphan. Any guidance or manual page would be appreciated. Cheers, TMS III

Hello, The handling of orphaned sections in LLD 8 has changed from GNU LD behavior (note that LLD 7 didn't show this behavior). I've reported this as: https://bugs.llvm.org/show_bug.cgi?id=42327 It's not clear to me however whether this is intentional or a regression when compared to LLD 7. As stated in that bug report it would be helpful for me to get some kind of documentation

On Fri, 21 Jun 2019 at 13:05, Rui Ueyama via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I think Geroge (cc'ed) knows better than me in that area. > > lld is underdocumented, and in particular there is virtually no documentation about its linker script support. Our basic strategy is to follow the GNU's documentation and the implementations unless it is too hard or

On Fri, Apr 18, 2014 at 06:56:57PM +0200, Patrik Horn?k wrote: > > yesterday I experienced following problem with my ext3 filesystem: > > - I had ext3 filesystem of the size of a few TB with journal. I correctly > unmounted it and it was marked clean. > > - I then ran fsck.etx3 -f on it and it did not find any problem. > > - After increasing size of its LVM volume by

Hi, it seems you got it right! I don't know if you read email I sent you before posting to the mailing list, but I accidentally diagnosed the cause... :) I've noticed that inodes fsck warned me about, at least ones that I checked, all have all four timestamps latest in 2010... The filesystem has maximum 1281998848 inodes, which is timestamp in august 2010. I don't know how it got

Hi, i've still these orhpaned entries and don't know where to remove them. Samba-tool drs showrepl [.] CN=Configuration,DC=local,DC=laurenz,DC=ws NTDS DN: CN=NTDS Settings\0ADEL:262e2471-dc01-4d71-ae5d-f71f9d8c2d5d,CN=SHELBY\0ADEL:72a698fc -6b93-41d1-9961-504008ea2415,CN=Servers,CN=Zuhause,CN=Sites,CN=Configuration ,DC=local,DC=laurenz,DC=ws DSA

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.

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 have two samba 4.1.9 as domain controllers. I want to join two new samba servers (Current version) as DC into the domain in order to demote the old ones. When I try to join as DC the first new samba, It can't synchronize because of orphaned objects in the samba 4.1.9. So, I want to remove such orphaned objects first. I can't do that using samba-tool dbcheck --fix Which command

The following shows up in the "orphaned page" list of the Wiki: http://wiki.dovecot.org/MboxLocking?action=show&redirect=MboxSoftwareLocks Does the description of Dovecot mbox locking still apply to current versions? If yes, it should be linked from the "Troubleshooting" page. -- Jim Garrison (jhg at acm.org) PGP Keys at http://www.jhmg.net RSA 0x04B73B7F DH 0x70738D88

Dear R Developers, the following CRAN packages do not cleanly pass R CMD check for quite some time now and did not have any updates since the time given. Several attempts by the CRAN admins to contact the package maintainers had no success. norm, 1.0-9, 2002-05-07, WARN sound, 0.6, 2002-08-31, WARN Bhat, 0.9-07, 2003-11-04, WARN HI, 0.1, 2003-11-04, WARN mmlcr, 1.3.2, 2003-11-15, WARN mvnmle,

Hello, yesterday I experienced following problem with my ext3 filesystem: - I had ext3 filesystem of the size of a few TB with journal. I correctly unmounted it and it was marked clean. - I then ran fsck.etx3 -f on it and it did not find any problem. - After increasing size of its LVM volume by 1.5 TB I resized the filesystem by resize2fs lvm_volume and it finished without problem. - But

Hi Due to an outage of one node, after bringing it up again, the node has some orphaned snapshosts, which are already deleted on the other nodes. How can I delete these orphaned snapshots? Trying the normal way produceses these errors: |[2023-08-08 19:34:03.667109 +0000] E [MSGID: 106115] [glusterd-mgmt.c:118:gd_mgmt_v3_collate_errors] 0-management: Pre Validation failed on B742. Please

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, i am seeing something interesting since the upgrade to 2.2.19/0.0.7a - I am experimenting with the am930 wireless driver and i am crashing on module exit. Everytime i reboot afterwards the var fs on /dev/hda8 is inconsistent [...] Checking all file systems... Parallelizing fsck version 1.21-WIP (01-Jun-2001) /dev/hda7: recovering journal /dev/hda7: clean, 39160/320640 files, 354596/640702

All, Sometimes when I do an rsync, it times out and leaves on orphaned process on the remote machine. I am running rsync over ssh using public key authentication. I synchronize about twenty-five machines, and this problem only appears on one of them. It worked until recently on this machine. I don't know what changed or what is different. I run rsync with a command line like this