search for: ram15

.../dev/ram13 RW /dev/ram13: block size is 1024 bytes /dev/ram13: No label detected Closed /dev/ram13 /dev/ram14: Not using O_DIRECT Opened /dev/ram14 RW /dev/ram14: block size is 1024 bytes /dev/ram14: No label detected Closed /dev/ram14 /dev/ram15: Not using O_DIRECT Opened /dev/ram15 RW /dev/ram15: block size is 1024 bytes /dev/ram15: No label detected Closed /dev/ram15 Opened /dev/sdb4 RW O_DIRECT /dev/sdb4: block size is 512 bytes /dev/sdb4: lvm2 label detected lvmcache: /dev/sdb4: now o...

...dy] Promise /VTrak M300i /2200 222ea000155eadda4 1:0:0:0 sdb 8:16 [ready] Promise /VTrak M300i /2200 dm-0 blacklisted dm-1 blacklisted hda blacklisted hdc blacklisted md0 blacklisted ram0 blacklisted ram10 blacklisted ram11 blacklisted ram12 blacklisted ram13 blacklisted ram14 blacklisted ram15 blacklisted ram1 blacklisted ram2 blacklisted ram3 blacklisted ram4 blacklisted ram5 blacklisted ram6 blacklisted ram7 blacklisted ram8 blacklisted ram9 blacklisted ===== path info sda (mask 0x1f) ===== bus = 1 dev_t = 8:0 size = 3503903232 vendor = Promise product = VTrak M300i rev = 2200 h:b:t:l...

...o test modems). I''ve set up thinks like this : -created a /var/lock.skel dir, containing the directory structure of /var/lock (emacs seems to need its own subdir) -at startup, create a ramdisk on mount it on /var/lock : #create a small ramdisk, mount /var/lock there dd if=/dev/zero of=/dev/ram15 bs=1k count=64 > /dev/null mke2fs -m0 /dev/ram15 64 > /dev/null mount /dev/ram15 /var/lock > /dev/null cp -raf /var/lock.skel/* /var/lock/ >/dev/null This way, creating a log file will not spinup the HD. Added benefit is that there won''t be stale locks after power failure......

...ls=03(HID ) Sub=00 Prot=00 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 6 Ivl=100ms ===== what I see in /sys/block ====== # ls /sys/block hda/ loop2/ loop6/ ram1/ ram13/ ram3/ ram7/ sdb/ sdf/ hdb/ loop3/ loop7/ ram10/ ram14/ ram4/ ram8/ sdc/ loop0/ loop4/ md0/ ram11/ ram15/ ram5/ ram9/ sdd/ loop1/ loop5/ ram0/ ram12/ ram2/ ram6/ sda/ sde/ ===== What udevadm (udevinfo) sees ===== # udevadm info -a -p /sys/devices/pci0000:00/0000:00:1d.2 /usb4/4-2 Udevinfo starts with the device specified by the devpath and then walks up the chain of parent devices. It...

...oes not exist here [root at odie ~]# ls /dev/ adsp????????? disk?????????? fd0u1040? fd0u830???? initctl? MAKEDEV parport2? ram14??? root??????? tty1?? tty21? tty33? tty45? tty57 ttyS2?????????? usbdev2.6_ep00? vcs1?? X0R agpgart?????? dsp??????????? fd0u1120? floppy????? input??? mapper parport3? ram15??? rtc???????? tty10? tty22? tty34? tty46? tty58 ttyS3?????????? usbdev2.6_ep05? vcs2?? zero audio???????? dsp1?????????? fd0u1440? floppy-fd0? kmsg???? md0 port????? ram2???? sequencer?? tty11? tty23? tty35? tty47? tty59 ttyUSB0???????? usbdev2.6_ep0b? vcs3 audio1??????? dvd??????????? fd0u1680? f...

Guys! Tomorrow in my "live" presentation at Linuxcon Xen Directions! I''ll show the Xen Live CD to the public! To celebrate! I want to share my last procedure to get and run Xen 4.0.1 on Ubuntu 10.04 64 bits, here we go: The procedure: 1- Install all the packages: aptitude update aptitude install bridge-utils build-essential libncurses5-dev dpkg-dev debhelper

...brw-r----- 1 root disk 1, 11 Mar 2 18:06 ram11 brw-r----- 1 root disk 1, 12 Mar 2 18:06 ram12 brw-r----- 1 root disk 1, 13 Mar 2 18:06 ram13 brw-r----- 1 root disk 1, 14 Mar 2 18:06 ram14 brw-r----- 1 root disk 1, 15 Mar 2 18:06 ram15 brw-r----- 1 root disk 1, 2 Mar 2 18:06 ram2 brw-r----- 1 root disk 1, 3 Mar 2 18:06 ram3 brw-r----- 1 root disk 1, 4 Mar 2 18:06 ram4 brw-r----- 1 root disk 1, 5 Mar 2 18:06 ram5 brw-r----- 1 root disk 1, 6 Mar 2 18:06 ram6...

Has anyone had issues starting xen0 on a md? I have installed it a few times now w/ and w/o raid. Anytime I have a raid1 mirror, Xen panics on boot when trying to mount /. It gets past waiting for /dev/md0 to appear. John _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Has anyone had issues starting xen0 on a md? I have installed it a few times now w/ and w/o raid. Anytime I have a raid1 mirror, Xen panics on boot when trying to mount /. It gets past waiting for /dev/md0 to appear. John _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...-- 1 0 0 1, 1 Jan 1 00:00 ram1 brw------- 1 0 0 1, 10 Jan 1 00:00 ram10 brw------- 1 0 0 1, 11 Jan 1 00:00 ram11 brw------- 1 0 0 1, 12 Jan 1 00:00 ram12 brw------- 1 0 0 1, 13 Jan 1 00:00 ram13 brw------- 1 0 0 1, 14 Jan 1 00:00 ram14 brw------- 1 0 0 1, 15 Jan 1 00:00 ram15 brw------- 1 0 0 1, 2 Jan 1 00:00 ram2 brw------- 1 0 0 1, 3 Jan 1 00:00 ram3 brw------- 1 0 0 1, 4 Jan 1 00:00 ram4 brw------- 1 0 0 1, 5 Jan 1 00:00 ram5 brw------- 1 0 0 1, 6 Jan 1 00:00 ram6 brw------- 1 0 0 1, 7 Jan 1 00:00 ram7 brw------- 1 0 0 1, 8 Jan 1 00...

.../dev/ram8???????????? [????? 16.00 MiB] ? /dev/ram9???????????? [????? 16.00 MiB] ? /dev/ram10??????????? [????? 16.00 MiB] ? /dev/ram11??????????? [????? 16.00 MiB] ? /dev/ram12??????????? [????? 16.00 MiB] ? /dev/ram13??????????? [????? 16.00 MiB] ? /dev/ram14??????????? [????? 16.00 MiB] ? /dev/ram15??????????? [????? 16.00 MiB] ? /dev/sdb1???????????? [?????? 1.82 TiB] LVM physical volume ? /dev/sdc1???????????? [???? 500.00 MiB] ? /dev/sdc2???????????? [?????? 4.00 TiB] LVM physical volume ? /dev/sdd1???????????? [?????? 4.00 TiB] LVM physical volume ? /dev/sde1???????????? [?????? 2.91 TiB]...

...brw-rw---- 1 root disk 1, 10 Dec 18 13:10 ram10 brw-rw---- 1 root disk 1, 11 Dec 18 13:10 ram11 brw-rw---- 1 root disk 1, 12 Dec 18 13:10 ram12 brw-rw---- 1 root disk 1, 13 Dec 18 13:10 ram13 brw-rw---- 1 root disk 1, 14 Dec 18 13:10 ram14 brw-rw---- 1 root disk 1, 15 Dec 18 13:10 ram15 brw-rw---- 1 root disk 1, 2 Dec 18 13:10 ram2 brw-rw---- 1 root disk 1, 3 Dec 18 13:10 ram3 brw-rw---- 1 root disk 1, 4 Dec 18 13:10 ram4 brw-rw---- 1 root disk 1, 5 Dec 18 13:10 ram5 brw-rw---- 1 root disk 1, 6 Dec 18 13:10 ram6 brw-rw---- 1 root disk 1, 7 Dec 18 13:10 ram7...

...brw-rw---- 1 root disk 1, 10 Nov 22 12:04 ram10 brw-rw---- 1 root disk 1, 11 Nov 22 12:04 ram11 brw-rw---- 1 root disk 1, 12 Nov 22 12:04 ram12 brw-rw---- 1 root disk 1, 13 Nov 22 12:04 ram13 brw-rw---- 1 root disk 1, 14 Nov 22 12:04 ram14 brw-rw---- 1 root disk 1, 15 Nov 22 12:04 ram15 brw-rw---- 1 root disk 1, 2 Nov 22 12:04 ram2 brw-rw---- 1 root disk 1, 3 Nov 22 12:04 ram3 brw-rw---- 1 root disk 1, 4 Nov 22 12:04 ram4 brw-rw---- 1 root disk 1, 5 Nov 22 12:04 ram5 brw-rw---- 1 root disk 1, 6 Nov 22 12:04 ram6 brw-rw---- 1 root disk 1, 7 Nov 22 12:04 ram7...

...MiB] > ? /dev/ram9???????????? [????? 16.00 MiB] > ? /dev/ram10??????????? [????? 16.00 MiB] > ? /dev/ram11??????????? [????? 16.00 MiB] > ? /dev/ram12??????????? [????? 16.00 MiB] > ? /dev/ram13??????????? [????? 16.00 MiB] > ? /dev/ram14??????????? [????? 16.00 MiB] > ? /dev/ram15??????????? [????? 16.00 MiB] > ? /dev/sdb1???????????? [?????? 1.82 TiB] LVM physical volume > ? /dev/sdc1???????????? [???? 500.00 MiB] > ? /dev/sdc2???????????? [?????? 4.00 TiB] LVM physical volume > ? /dev/sdd1???????????? [?????? 4.00 TiB] LVM physical volume > ? /dev/sde1??????...

On Thu, Jun 12, 2014 at 05:08:37PM +0530, abhishek jain wrote: > Hi Rich > > I have all the virtio modules available in the kernel but I'm getting the > same result . It doesn't appear to be using any kernel modules. I would have expected to see output such as this: supermin: internal insmod virtio.ko It seems as if you might not be setting SUPERMIN_MODULES; or maybe you

...?????????? [????? 16.00 MiB] >> ? /dev/ram10??????????? [????? 16.00 MiB] >> ? /dev/ram11??????????? [????? 16.00 MiB] >> ? /dev/ram12??????????? [????? 16.00 MiB] >> ? /dev/ram13??????????? [????? 16.00 MiB] >> ? /dev/ram14??????????? [????? 16.00 MiB] >> ? /dev/ram15??????????? [????? 16.00 MiB] >> ? /dev/sdb1???????????? [?????? 1.82 TiB] LVM physical volume >> ? /dev/sdc1???????????? [???? 500.00 MiB] >> ? /dev/sdc2???????????? [?????? 4.00 TiB] LVM physical volume >> ? /dev/sdd1???????????? [?????? 4.00 TiB] LVM physical volume >&g...

...-- 1 0 0 1, 1 Dec 11 21:57 ram1 brw------- 1 0 0 1, 10 Dec 11 21:57 ram10 brw------- 1 0 0 1, 11 Dec 11 21:57 ram11 brw------- 1 0 0 1, 12 Dec 11 21:57 ram12 brw------- 1 0 0 1, 13 Dec 11 21:57 ram13 brw------- 1 0 0 1, 14 Dec 11 21:57 ram14 brw------- 1 0 0 1, 15 Dec 11 21:57 ram15 brw------- 1 0 0 1, 2 Dec 11 21:57 ram2 brw------- 1 0 0 1, 3 Dec 11 21:57 ram3 brw------- 1 0 0 1, 4 Dec 11 21:57 ram4 brw------- 1 0 0 1, 5 Dec 11 21:57 ram5 brw------- 1 0 0 1, 6 Dec 11 21:57 ram6 brw------- 1 0 0 1, 7 Dec 11 21:57 ram7 brw------- 1 0 0 1, 8 Dec 11 21...

Unfortunately, placing the link into the /boot does not work. libguestfs-test-tool failes with the same message: ************************************************************ * IMPORTANT NOTICE * * When reporting bugs, include the COMPLETE, UNEDITED * output below in your bug report. *

...---- 1 0 0 1, 1 Feb 27 02:31 ram1 brw------- 1 0 0 1, 10 Feb 27 02:31 ram10 brw------- 1 0 0 1, 11 Feb 27 02:31 ram11 brw------- 1 0 0 1, 12 Feb 27 02:31 ram12 brw------- 1 0 0 1, 13 Feb 27 02:31 ram13 brw------- 1 0 0 1, 14 Feb 27 02:31 ram14 brw------- 1 0 0 1, 15 Feb 27 02:31 ram15 brw------- 1 0 0 1, 2 Feb 27 02:31 ram2 brw------- 1 0 0 1, 3 Feb 27 02:31 ram3 brw------- 1 0 0 1, 4 Feb 27 02:31 ram4 brw------- 1 0 0 1, 5 Feb 27 02:31 ram5 brw------- 1 0 0 1, 6 Feb 27 02:31 ram6 brw------- 1 0 0 1, 7 Feb 27 02:31 ram7 brw------ 1 0 0 1, 8 Feb 27 02:31 ram8 brw-...

...brw-r----- 1 root disk 1, 10 Sep 28 22:57 ram10 brw-r----- 1 root disk 1, 11 Sep 28 22:57 ram11 brw-r----- 1 root disk 1, 12 Sep 28 22:57 ram12 brw-r----- 1 root disk 1, 13 Sep 28 22:57 ram13 brw-r----- 1 root disk 1, 14 Sep 28 22:57 ram14 brw-r----- 1 root disk 1, 15 Sep 28 22:57 ram15 brw-r----- 1 root disk 1, 2 Sep 28 22:57 ram2 brw-r----- 1 root disk 1, 3 Sep 28 22:57 ram3 brw-r----- 1 root disk 1, 4 Sep 28 22:57 ram4 brw-r----- 1 root disk 1, 5 Sep 28 22:57 ram5 brw-r----- 1 root disk 1, 6 Sep 28 22:57 ram6 brw-r----- 1 root disk 1, 7 Sep 28 22:57 ram7...