similar to: detail explain of file creation process

Hi, I have a server configured as follows: a standard 2.4.18 kernel, IDE discs, 1Gb RAM (not all used), load avg around 1-2. a large partition, formatted reiserfs within large partition are 80 300Mb loopback file systems, formatted ext3. I got the following assertion yesterday which forced a lot of processes into D state. I'm not sure how easy it is to reproduce this problem.

Hi I have strange problem. same traffic control rules when i started it manual they work OK, but when i started it from crontab / twice per day / doesn''t work correctly ... look like delete rules doesn''t work ... any ideas where to look for problem ? i use debian sarge Linux 2.6 kernel , #!/bin/bash TC=/sbin/tc DEV=eth1 echo "Delete all rules" $TC qdisc

While compiling two kernels and untarring a third, my root fs was remounted r/w and I got the following in dmesg (kernel 2.4.19-pre9): EXT3-fs error (device ide0(3,2)) in ext3_new_inode: error 28 Aborting journal on device ide0(3,2). ext3_abort called EXT3-fs abort (device ide0(3,2)): ext3_journal_start: Detected aborted journal. Remounting filesystem read-only Remounting filesystem read-only

I'm looking for some recommendations on where to go with a problem i'm running across. A filesystem under load put itself in readonly mode and the following can be found under dmesg.. any suggestions on root cause? hardware wise it's got a pair of PATA drives connected to a 3ware card in RAID10 configuration. EXT3-fs error (device dm-4): ext3_add_entry: bad entry in directory

I got this error in my log reports this morning, from the machine I use as my firewall. This is the first time it has occurred, but the machine is running a very new kernel: Linux fendrian.rimspace.net 2.6.0-test11-fendrian #1 Wed Dec 10 22:25:59 EST 2003 i486 GNU/Linux The kernel was up to date as per the CVS repository at that point. This was just before the CDROM_SEND_PACKET IOCTL fix went

Hello: I am making a DVD recovery system using mkisofs and isolinux, so i using this command: mkisofs -l -r -J -V "Lavel" -hide-rrmoved -v -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -o image.iso ./ In the directory y have a "Image" folder, there i put the partimage files. The result is a image.iso with a size depending

Hi, i am seeing an oops (every couple of days) on a UP PII system with SCSI disks, Kernel 2.2.19 and ext3 0.0.6b. All oops output passed the klogd thus i cant anymore pipe it through ksymoops - I ensured klogd got the correct System.map so the result should be reliable. Apr 25 17:03:10 Unable to handle kernel paging request at virtual address 8efd1fc8 current->tss.cr3 = 0981e000, %%cr3 =

On Sat, Dec 24, 2005 at 11:03:36PM +0300, Andrey J. Melnikoff (TEMHOTA) wrote: > Hello. Hi Andrey, > Please, CC me, i'm not subscribed. > > Kernel 2.6.15-rc6 OOPS: > > kernel: general protection fault: 0000 [#1] > kernel: SMP > kernel: Modules linked in: ipt_REDIRECT ipt_LOG ipt_TOS ipt_TCPMSS ipt_tos > ip_nat_ftp ipt_tcpmss iptable_nat ip_nat iptable_mangle

Hi, gdbserver-xen coredump after i step through a few lines of code. build dom0 with debug_domu. Enable debuginfo and frame pointer for dom U and attach the domu with gdbserver . In gdb put breakpoint at say sys_open and after going through few lines of code gdbserver-xen coredumps. The resulting core file has the below stack $gdb /usr/local/bin/gdbserver-xen ./core GNU gdb 6.3-debian

Unlink files, symlinks, FIFOs, devices etc. (except directories) before writing them when extracting CPIOs. This stops weird behaviour like: 1) writing through symlinks created in earlier CPIOs. eg foo->bar in the first CPIO. Having foo as a non-link in a subsequent CPIO, results in bar being written and foo remaining as a symlink. 2) if the first version of file foo is larger

Using fsdlm/ocfs2_controld.cman, I've rerun the test I've been having problems with on 2.6.30-rc1. After running for several minutes in the same directory on three nodes, the test hangs, and I collect the following information: bull-01 ------- 3053 S< [ocfs2dc] ocfs2_downconvert_thread 3054 S< [dlm_astd] dlm_astd 3055 S< [dlm_scand]

Dear all. I'm experiencing a weird crash with one of our desktop running CentOS 5.1 We have 5 machines identical, onle one has this problem. Right after it starts, it will kernel panic. Unfortunately, from the backtrace this is all I've managed to get : serial port isn't working. So it's a manual copy of what the screen show. [<c04721f3>] sync_buffer+0x0/0x33

BUG: soft lockup detected on CPU#0! Pid: 2213, comm: smbiod EIP: 0061:[<f4990f2e>] CPU: 0 EIP is at smbiod+0x116/0x16d [smbfs] EFLAGS: 00000246 Tainted: GF (2.6.16-xen-automount #1) EAX: 00000000 EBX: f4996400 ECX: f2c99f68 EDX: f2c98000 ESI: f2c98000 EDI: c06f5780 EBP: f2c99fb8 DS: 007b ES: 007b CR0: 8005003b CR2: b7f77000 CR3: 326e2000 CR4: 00000640

Hi All, I've been trying to trace the cause of a hang on a 5.6 i386 system. After running for almost a year, it hung last week, when I plugged in a screen it was blank, machine was unresponsive to the keyboard, over the network ssh and other daemons didn't respond but the thing has two network cards and routing from one to the other was still working. So the kernel was up and I

I'm getting kernel crashes on a new machine since it went into production some weeks ago. How can I troubleshoot this? I suspect a hardware problem, but I know too few about the kernel and kernel debugging on Linux to know how I can nail this down with debugging software. Just for reference of what kind these oopses are I quote the last two. The symptom is that the machine stops

I''m having an issue forwarding through an Intel on-board graphics adapter. This is on a Dell Optiplex 780 with 8GB of RAM. The pass-through works perfectly fine if I have 2GB of RAM assigned to the HVM domU. If I try to assign 3GB or 4GB of RAM, I get the following on the console: [ 41.222073] br0: port 2(vif1.0) entering forwarding state [ 41.269854] (cdrom_add_media_watch()

I''m having an issue forwarding through an Intel on-board graphics adapter. This is on a Dell Optiplex 780 with 8GB of RAM. The pass-through works perfectly fine if I have 2GB of RAM assigned to the HVM domU. If I try to assign 3GB or 4GB of RAM, I get the following on the console: [ 41.222073] br0: port 2(vif1.0) entering forwarding state [ 41.269854] (cdrom_add_media_watch()

From: "Xiaowei.Hu" <xiaowei.hu at oracle.com> ocfs2_block_group_alloc_discontig() disables chain relink by setting ac->ac_allow_chain_relink = 0 because it grabs clusters from multiple cluster groups. It doesn't keep the credits for all chain relink,but ocfs2_claim_suballoc_bits overrides this in this call trace:

I have several CentOS5 hosts in a VMware ESX 3.5.0 226117 environment using iSCSI storage. Recently we've begun to experience journal aborts resulting in remounted-read-only filesystems as well as other filesystem issues - I can unmount a filesystem and force a check with "fsck -f" and occasionally find errors. I've found -

Le 07/07/2017 ? 16:52, Duncan Murdoch a ?crit : > On 07/07/2017 9:54 AM, Serguei Sokol wrote: >> Le 07/07/2017 ? 01:09, Duncan Murdoch a ?crit : >>> On 06/07/2017 6:44 PM, Sokol Serguei wrote: >>>> Duncan Murdoch has written at Thu, 6 Jul 2017 13:58:10 -0400 >>>>> On 06/07/2017 5:21 AM, Serguei Sokol wrote: >>>>>> I propose the