search for: 1m

...g about 100M files totaling about 8.5TiBytes. To see how ext3 would perform with large numbers of files I've written a test program which creates a configurable number of files into a configurable number of directories, reads from those files, lists them and then deletes them. Even up to 1M files ext3 seems to perform well and scale linearly; the time to execute the program on 1M files is about double the time it takes it to execute on .5M files. But past 1M files it seems to have n^2 scalability. Test details appear below. Looking at the various options for ext3 nothing jumps o...

I am getting following error while run my rails app in my server ActionView::Template::Error (You did not provide both required access keys. Please provide the access_key_id and the secret_access_key.): -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

...ipt. tc qdisc del dev eth0 root tc qdisc add dev eth0 root handle 1: htb default 50 tc class add dev eth0 parent 1: classid 1:1 htb rate 32kbit ceil 32kbit tc filter add dev eth0 protocol ip parent 1:0 prio 100 u32 match ip src 10.4.0.0/16 match ip dst 0.0.0.0/0 classid 1:1 If I try to transfer a 1M file from C to A: [root@localpost tmp]# wget 192.168.0.23/1M --09:22:32-- http://192.168.0.23/1M => `1M.8'' Connecting to 192.168.0.23:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1,024,000 [text/plain] 100%[=====================>] 1,024,000 183.12K/s...

-bash-3.2$ zfs share tank cannot share ''tank'': share(1M) failed -bash-3.2$ how do i figure out what''s wrong? This message posted from opensolaris.org

Hi all. I''m now try to read and write puseud physical memory of domU from Dom0 with xenaccess(this is using libxc). #http://xenaccess.sourceforge.net/ With xenaccess, I''m succeeded read and writing almost of the memory. But It fail when I try to access head 1M region and some bit regions. To be precise, xc_map_foreign_range() of libxc returns error code. ** <javascript:goWordLink("to")> What''s allocated on head 1M region of domU? #and , Can I get a document about memory allocation of dom0 and DomU somewhere? regards. *********...

Hi, I noticed that the glusterfs client tries to set ulimit -n to 1M. When I run booster with non-privileged user, the following line appears several times in the log file: [2009-09-14 09:15:22] W [client-protocol.c:6010:init] brick-0-0-0: WARNING: Failed to set 'ulimit -n 1M': Operation not permitted When I run it with root, there's no such compla...

Hi, I have btrfs volume, shared via samba. I have a directory of documents that I want to backup on my server. win7 reports a maximum of ~3.10MB/s transfer transferring the same directory on a ext4 samba share I get 25MB/s + Any ideas? Is it like that because of how btrfs works and is setup? Thanks, -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body

...126M gran_size: 64K chunk_size: 128K num_reg: 10 lose cover RAM: 126M gran_size: 64K chunk_size: 256K num_reg: 10 lose cover RAM: 126M gran_size: 64K chunk_size: 512K num_reg: 10 lose cover RAM: 126M gran_size: 64K chunk_size: 1M num_reg: 10 lose cover RAM: 126M gran_size: 64K chunk_size: 2M num_reg: 10 lose cover RAM: 126M *BAD*gran_size: 64K chunk_size: 4M num_reg: 10 lose cover RAM: -2M *BAD*gran_size: 64K chunk_size: 8M num_reg: 10 lose cover RAM: -2M gran_size: 64K chunk_si...

...num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 256K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 512K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 1M num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 2M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 4M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size:...

...= ~ time | id, correlation=cs3,data=gg.data.frame,method="ML",weights=varIdent(form= ~id)) After ~ 200 - 300 loops the process is killed by the OS with the following errors Mar 17 08:55:56 1A:helmholtz unix: ALERT: R.bin [1157] - out of logical swap space during stack growth - see swap(1M) [filter /usr/sbin/klogpp failed: killed by signal 9] Mar 17 08:55:56 1A:helmholtz unix: ALERT: R.bin [1157] - out of logical swap space during stack growth - see swap(1M) Mar 17 08:55:56 1A:helmholtz unix: ALERT: R.bin [1157] - out of logical swap space during stack growth - see swap(1M) Mar 17 08...

...-- ----- ----- ----- 1 272K 17.0G 17.0G 17.0G 272K 17.0G 17.0G 17.0G 2 32.7K 2.05G 2.05G 2.05G 65.6K 4.10G 4.10G 4.10G 4 15 960K 960K 960K 71 4.44M 4.44M 4.44M 8 4 256K 256K 256K 53 3.31M 3.31M 3.31M 16 1 64K 64K 64K 16 1M 1M 1M 512 1 64K 64K 64K 854 53.4M 53.4M 53.4M 1K 1 64K 64K 64K 1.08K 69.1M 69.1M 69.1M 4K 1 64K 64K 64K 5.33K 341M 341M...

..._reg: 10 lose cover RAM: 56M gran_size: 64K chunk_size: 128K num_reg: 10 lose cover RAM: 56M gran_size: 64K chunk_size: 256K num_reg: 10 lose cover RAM: 56M gran_size: 64K chunk_size: 512K num_reg: 10 lose cover RAM: 56M gran_size: 64K chunk_size: 1M num_reg: 10 lose cover RAM: 56M gran_size: 64K chunk_size: 2M num_reg: 10 lose cover RAM: 56M gran_size: 64K chunk_size: 4M num_reg: 10 lose cover RAM: 56M gran_size: 64K chunk_size: 8M num_reg: 10 lose cover RAM: 56M gran_size: 64K chunk_size...

...ds in 1048576+0 records out 1073741824 bytes (1.1 GB) copied, 395.183 s, 2.7 MB/s 2097152+0 records in 2097152+0 records out 1073741824 bytes (1.1 GB) copied, 395.184 s, 2.7 MB/s The underlying block device is quite quick: ng-vvv1:~# dd if=/dev/mapper/3600a0b800067df83000003ba4ba0f5ef bs=1k count=1M | dd of=/dev/null 1048576+0 records in 1048576+0 records out 2097152+0 records in 2097152+0 records out 1073741824 bytes (1.1 GB) copied, 6.32306 s, 170 MB/s 1073741824 bytes (1.1 GB) copied, 6.32293 s, 170 MB/s Here is the environment: * Infrastructure: two nodes, each with two port FC card cone...

...26.442620] [TTM] size: 131072 [ 126.446012] [TTM] available_caching: 0x00070000 [ 126.450884] [TTM] default_caching: 0x00010000 [ 126.458674] [TTM] Failed to find memory space for buffer 0xffff97a0bca01400 eviction [ 126.466453] [TTM] No space for ffff97a0bca01400 (342 pages, 1368K, 1M) [ 126.472969] [TTM] placement[0]=0x00070002 (1) [ 126.477489] [TTM] has_type: 1 [ 126.480800] [TTM] use_type: 1 [ 126.484106] [TTM] flags: 0x0000000A [ 126.487932] [TTM] gpu_offset: 0x00000000 [ 126.492191] [TTM] size: 131072 [ 126.495585] [TTM] available_caching:...

Hi: on a niagara platform, right after invokation of the plockstat(1M) for monitoring all events to a specific user-land process. It locks all monitored user-land processes pointer is very appreciated Thanks This message posted from opensolaris.org

Author: rmesta Repository: /hg/zfs-crypto/gate Revision: 76b3a89dc4ebc9f389aa37dd4f7e76275266630c Log message: PSARC 2005/487 sysidtool(1m) Integrated NFSv4 Prompts 6231897 ON changes in support of 5110062: nuke sysidnfs4(1m) Files: create: deleted_files/usr/src/cmd/fs.d/nfs/sysidnfs4/Makefile create: deleted_files/usr/src/cmd/fs.d/nfs/sysidnfs4/config_nfs4.c create: deleted_files/usr/src/cmd/fs.d/nfs/sysidnfs4/config_nfs4.h crea...

...ng at official (?) binary > https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.03/syslinux-6.03-pre11.tar.xz > I see that their size is also more than 64K Actually, there is *no* 64KiB limit on btrfs. Look at btrfs-progs (ctree.h:830): " /* * We don't want to overwrite 1M at the beginning of device, even though * there is our 1st superblock at 64k. Some possible reasons: * - the first 64k blank is useful for some boot loader/manager * - the first 1M could be scratched by buggy partitioner or somesuch */ #define BTRFS_BLOCK_RESERVED_1M_FOR_SUPER ((u64)1024 * 10...

.../sys/mtio.h the log file (part of it): . . . excluding directory lib/nsr because of pattern */nsr* . . . excluding file sbin/nsr_shutdown because of pattern */nsr* excluding file sbin/nsr_support because of pattern */nsr* excluding file sbin/nsradmin because of pattern */nsr* . . . share/man/man1m/nsr.1m is newer share/man/man1m/nsr_crash.1m is newer share/man/man1m/nsr_shutdown.1m is newer share/man/man1m/nsradmin.1m is newer share/man/man1m/nsralist.1m is newer share/man/man1m/nsrarchive.1m is newer share/man/man1m/nsrcap.1m is newer . . .

...ee_bits == move_len) { + i -= move_len; *goal_bit = i; *phys_cpos = base_cpos + i; break; @@ -1020,18 +1021,19 @@ int ocfs2_ioctl_move_extents(struct file *filp, void __user *argp) context->range = &range; + /* + * ok, the default theshold for the defragmentation + * is 1M, since our maximum clustersize was 1M also. + * any thought? + */ + if (!range.me_threshold) + range.me_threshold = 1024 * 1024; + + if (range.me_threshold > i_size_read(inode)) + range.me_threshold = i_size_read(inode); + if (range.me_flags & OCFS2_MOVE_EXT_FL_AUTO_DEFRAG) { contex...

The dtrace(1M) manpage seems to be incorrect, it states: -32 | -64 The D compiler produces programs using the native data model of the operating system kernel. You can use the isainfo -b command to determine the current operating system data model. If the -3...