similar to: Periodic fsck's fail but all is OK.

Greetings! Need your help fellow penguins! Strange behavior with fsck.ext3: how to remove a long orphaned inode list? After copying data over from one old RAID to another new RAID with rsync, the dump command would not complete because of filesystem errors on the new RAID. So I ran fsck.ext3 with the -y option and it would just run in an infinite loop restarting itself and then trying to correct

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

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

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

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

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

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

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

Resending after adding another patch to display delayed orphan scan statistics.

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

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

If you use the EPEL repository, please read https://lists.fedoraproject.org/pipermail/epel-announce/2014-November/000032.html TL;DR: There are a large number of orphaned/unmaintained packages in EPEL across the 5, 6, and 7 trees. These packages will be removed from EPEL unless they are picked up by a packager. Packages that *depend* on an orphaned package will be removed as well to ensure

Christian, Just a quick heads up warning that something seems to be amiss on the Snom 200 running v2.03h code. The Message Waiting Indicator is blinking (due to a voicemail left in Asterisk) as its suppose to. Some time later the LED stops blinking (as though no voicemail); then later it starts blinking again. I left a voicemail to x3008 (button 2) this morning at 8:48am, and purposefully have

I'd second Jim's feature request - it would be useful to be able to disable this in CI and elsewhere. The concept of using an "unusual" version component such as a very large number does a nice job of indicating "unusual" and serves as a blocker for submitting work-in-progress to CRAN by mistake (hence the validation in 'R CMD check'). Another point, which I

Resending after implementing review comments.

I have the following quick-and-dirty hack in my model: def after_destroy # search for orphaned tags and delete them orphans = Resource.tags_count :count => ''= 0'' orphans.keys.each {|tag| Tags.find_by_name(''tag'').destroy} end It''s nice from a readable code perspective, but it seems inefficient - is there some way to do this with only one

On unlink, all nodes check for the dentry in dcache and if present they mark the node as unlinked. The last node that purges the inode will clean it from orphan directory. When there is a memory pressure, a dentry may not be around and hence the inode is not marked as deleted and this will lead the file to be in the orphan directory till the slot is re-used during next mount. This patch initiates

Hello... it was put under my attention that a partition we have in one of our production system was displaying wrong size with df command.... 123 GB... but in fact the size of all the files is a mere 15 GB.... What is going on? Shall we use ocfs.fsck to fix that? Is strange... Thanks for any comment.... Raymundo Garcia ________________________________ The information contained in this message

On a customer's machine running SuSE 9.2, the size of the occupied space on the harddisk is reported incorrectly by "df -h". After we noticed the problem, I rebooted the machine and had it checked by "e2fsck" (check forced with "tune2fs -C 40", we are not on location). Right after the reboot I proceeded as follows, but I could not find any information about

Hi folks, For my app, I needed to modify acts_as_tree (ActiveRecord::Acts::Tree) such that deleting a node would orphan sub-nodes, rather than deleting them. This is accomplished simply by allowing a :dependent option to the acts_as_tree method so that it can be set to :nullify. For my app, I simply did this by adding a file tree.rb to my lib directory and requiring it in the model. A number