search for: 98304

Hi all, I am running the current xen-unstable and had the following error message when trying to create domain1. # ./xenctl script -f/etc/xen-mynewdom Domain defaults: name XenoLinux size 98304 vifs 1 domainImage /boot/xenolinux.gz domainInitRD null rootDevice /dev/hda5 rootArgs rw usrDevice null NWIP 169.254.1.0+ NWGW 169.254.1.0 NWMask 255.255.0.0 MaxDomainNumber 1000 NWNFSServer 169....

...referen.png ] I'm showing sound driver and prefences because while i'm starting wow using console with wine i got this kind of error messages on when the problem above occurs : > > . > . > err:dsound:DSOUND_MixOne Fatal error. Under/Overflow? primary_done=29680, mixpos=79792/98304 (79792/98304), primary_mixpos=7200, writepos=10288, mixlen=0 > err:dsound:DSOUND_MixOne Fatal error. Under/Overflow? primary_done=29680, mixpos=70912/108116 (16288/24832), primary_mixpos=7200, writepos=10288, mixlen=0 > err:dsound:DSOUND_MixOne Fatal error. Under/Overflow? primary_done=29680,...

...echo "testb 1 117330000" | sudo debugfs /dev/sdc | grep "marked in use" has delivered 102595007 lines (containing block numbers marked as "used"). I tried to learn more about blocks marked as "marked in use" but not by a known file, and echo "icheck 98304 98305" | sudo debugfs /dev/sdc returned debugfs: icheck 98304 98305 Block Inode number 98304 <block not found> 98305 <block not found> Could somebody explain to be what the purpose of these 11,656,064 blocks is that don't belong to an inode but are still marked as us...

Hi, I am currently running a 10 Node OCFS2 Cluster (version 1.3.9-0ubuntu1) on Ubuntu Server 8.04 x86_64. Linux n1 2.6.24-24-server #1 SMP Tue Jul 7 19:39:36 UTC 2009 x86_64 GNU/Linux The Cluster is connected to a 1Tera iSCSI Device presented by an IBM 3300 Storage System, running over a 1Gig Network. Mounted on all nodes: /dev/sdc1 on /cfs1 type ocfs2

Hello everybody, I am new to this list, so welcome everybody. Last 2 week I had two harddisk crashes with my ext2 file system. This is what sort of happed with both of the disk: I pluged in my USB to SATA converter in my harddisk that has an ext2 filesystem. I mounted the partition, went to a directory that had a DVD image. I mounted the dvd image in the same directory and started watching the

...Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 4643968 inodes, 9277344 blocks 463867 blocks (5.00%) reserved for the super user First data block=0 284 block groups 32768 blocks per group, 32768 fragments per group 16352 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624 Writing inode tables: done Creating journal (32768 blocks): mkfs.ext3: Device or resource busy while trying to create journal zsh: exit 1 mkfs.ext3 /dev/md0 Could you help...

...ive window advertised by NFS client XXXXXXX is 5888. This is less than the recommended value of 32768 bytes. You should increase the TCP receive buffer size for NFS on the client. Some googling around got me to check these values for TCP: # sysctl net.ipv4.tcp_mem net.ipv4.tcp_mem = 98304 131072 196608 # sysctl net.ipv4.tcp_rmem net.ipv4.tcp_rmem = 4096 87380 4194304 # sysctl net.ipv4.tcp_wmem net.ipv4.tcp_wmem = 4096 16384 4194304 So these seem fine to me (i.e., the max is greater than 32768). Is there an NFS (as opposed to TCP) setting I s...

...ole/limit'': ''1048576'', ''vm'': ''/vm/c73d7a4b-4747-fe91-dbc4-0408183a9456'', ''domid'': ''10'', ''cpu/0/availability'': ''online'', ''memory/target'': ''98304'', ''store/ring-ref'': ''223145'', ''store/port'': ''1''} [2006-04-11 20:53:39 xend.XendDomainInfo] DEBUG (__init__:988) XendDomainInfo.handleShutdownWatch [2006-04-11 20:53:39 xend.XendDomainInfo] WARNING (__init__:988) Domain...

...g vorbis -- it will happen when I have time to write the script to convert the 1000s of files in my playlist - but with a pregnant wife and four kids - time is not something I have a lot of :) -- that I can do? I made the following changes: ices-playlist.xml: <encode> <nominal-bitrate>98304</nominal-bitrate> <maximum-bitrate>131072</maximum-bitrate> <managed>1</managed> <samplerate>44100</samplerate> <channels>2</channels> </encode> ices.conf: <Bitrate>96</Bitrate> <Reencode>0</Reencode> <Samplerate...

...with the following error in error.log: [crit] (28)No space left on device: mod_jk: could not create jk_log_lock With Apache not running, there're a lot of semaphores left behind by Apache, e.g.: ------ Semaphore Arrays -------- key semid owner perms nsems 0x00000000 98304 root 600 1 0x00000000 131073 apache 600 1 0x00000000 163842 apache 600 1 0x00000000 196611 apache 600 1 0x00000000 229380 apache 600 1 0x00000000 786437 root 600 1 ... ... ... /proc/sys/kernel/sem has the follo...

...68.1.1 winbind separator = # winbind cache time = 60 winbind enum users = Yes winbind enum groups = Yes winbind use default domain = Yes dns forwarder = 192.168.1.1 create mask = 0666 directory mask = 0777 socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=98304 SO_SNDBUF=98304 getwd cache = yes use sendfile = true min receivefile size = 16384 aio read size = 16384 aio write size = 16384 aio write behind = yes veto files = .* veto oplock files = /*.mdb/*.MDB/*.mde/*.MDE/ oplocks = Yes msdfs root = Yes vfs objects = zfsacl,...

While investigating my earlier Sendmail confusion I noticed these files: # ll /var/lib/imap/db/ total 15952 -rw------- 1 cyrus mail 16384 Jan 22 04:02 __db.001 -rw------- 1 cyrus mail 663552 Jan 22 04:02 __db.002 -rw------- 1 cyrus mail 98304 Jan 22 04:02 __db.003 -rw------- 1 cyrus mail 22568960 Jan 22 04:02 __db.004 -rw------- 1 cyrus mail 32768 Jan 22 04:02 __db.005 -rw------- 1 cyrus mail 64 Jan 22 04:02 log.0000000001 The date/time stamps suggest that these files were create by a cron job the day after I installed Cen...

...a live usb and run the short and long SMART tests on both drive. No problems reported but I know that can be misleading, so I'm going to have to gather some evidence before I try to return these drives. I run badblocks in destructive mode on both drives as follows badblocks -w -b 4096 -c 98304 -s /dev/sda badblocks -w -b 4096 -c 98304 -s /dev/sdb Come back the next day and see that no errors are reported. Er thats odd. I check the SMART data in case badblocks activity has triggered something. Nope. Maybe I screwed up the install somehow? So I start again and repeat the install pr...

I'm trying to use R for some of the analysis shown in Box, Hunter and Hunter (1979, I believe) using the aov function. I'm using the first example in chapter 6, where they are determining the analysis of varience between 4 treatments. In this example, the are determineing the analysis between and within treatments, which I can get by aov(response~treatment+Error(treatment)) Where

...evant client system, or run 'cat /proc/cmdline' in the booted system). If the server boots with Syslinux, this method would apply to it too. A possible SYSAPPEND statement could be: SYSAPPEND 0x18000 or its decimal alternative (in case the hex value fails for some reason): SYSAPPEND 98304 should provide: BIOSVENDOR= BIOS vendor name BIOSVERSION= BIOS version Regards, Ady. PS: Could the issue with booting Xen be not related to mboot.c32, but rather to something else (for instance, to something like the current "keeppxe" failing)? > _______________________...

...t;start":0,"length":32768,"data":false,"zero":true} +{"start":32768,"length":32768,"data":true,"zero":false} +{"start":65536,"length":32768,"data":true,"zero":true} +{"start":98304,"length":32768,"data":false,"zero":true} +{"start":131072,"length":32768,"data":true,"zero":false} +{"start":163840,"length":98304,"data":false,"zero":true} +{"start":262144,&quot...

...lock. I am running Fedora Core 6. I am booting off the Fedora Core 6 Rescue CD in order to try to fix things (my system isn't bootable.) Doing a e2fsck /dev/hda2 tells me that the superblock is corrupt. When I do a mke2fs -n /dev/hda2, it tells me that other backups are stored on 32768, 98304, 16840, 229376, 294912, 819200, 884736, 1605632, 265???? (cut off), 4096000, 7962624, 11239424, 20480000, 23887872. When I try doing a e2fsck -b xxx /dev/hda2, on any of the superblocks <= 4096000 I get the message that it's corrupted. When I do >= 7962625, I get "Invalid argume...

...53 2008 ./ drwxr-x--- 3 root wheel 512 Oct 27 07:57:42 2008 ../ -rw------- 1 root wheel 24576 Oct 27 13:00:01 2008 __db.001 -rw------- 1 root wheel 57344 Oct 27 13:00:01 2008 __db.002 -rw------- 1 root wheel 270336 Oct 27 13:00:01 2008 __db.003 -rw------- 1 root wheel 98304 Oct 27 13:00:01 2008 __db.004 -rw------- 1 root wheel 49152 Oct 27 13:00:01 2008 __db.005 -rw------- 1 root wheel 32768 Oct 26 19:47:37 2008 expire.db -rw------- 1 root wheel 10485760 Oct 27 14:22:08 2008 log.0000000001 It contains the familiar BDB files, so I think it works, althou...

...ount option, perhaps there are other tweaks you've made at mkfs time which could change the geometry from what I see above. dumpe2fs -h output might show us that. It could also be open but unlinked files, or unprocessed orphan inodes after a crash. Have you run e2fsck? > debugfs: icheck 98304 98305 > Block Inode number > 98304 <block not found> > 98305 <block not found> icheck won't find an inode number for internal metadata; it's not associated with any inode. > Do I have a chance other than reformatting the drive to get back this > space? I...

...el= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 1050400 inodes, 2098482 blocks 0 blocks (0.00%) reserved for the super user First data block=0 65 block groups 32768 blocks per group, 32768 fragments per group 16160 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 File size limit exceeded -------------------------------------------------- -------------- fdisk -l /dev/sdb ----------------- Disk /dev/sdb: 255 heads, 63 sectors, 4462 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start...