WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Weird tmpfs behavior -- getting trashed

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Weird tmpfs behavior -- getting trashed
From: Eric Brown <yogieric@xxxxxxx>
Date: Wed, 21 Sep 2005 23:46:54 -0700
Cc: Don Armstrong <don@xxxxxxxxxxxxxxxx>
Delivery-date: Thu, 22 Sep 2005 06:44:44 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
The symptom we're seeing is a trashed resolv.conf. However, it looks like is something stomped all over the tmpfs.

Every file in the /dev/shm was stomped on, including
/dev/shm/network/ifstate:

$ hexdump -C dev/shm/network/ifstate
00000000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
00000010
$ hexdump -C dev/shm/resolvconf/resolv.conf.bad
00000000 a4 81 00 00 21 00 00 00 2c 57 1e 43 1e 8d 1f 43 |....!...,W.C...C| 00000010 e9 bc 78 41 00 00 00 00 00 00 01 00 08 00 00 00 |..xA............| 00000020 00 00 00 00 00 00 00 00 ed 3d 28 00 00 00 00 00 |.........=(.....| 00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000060 00 00 00 00 a1 8d 33 c5 00 00 00 00 00 00 00 00 |...... 3.........| 00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00000080 a4 81 00 00 21 01 00 00 2c 57 1e 43 1e 8d 1f 43 |....!...,W.C...C| 00000090 e9 bc 78 41 00 00 00 00 00 00 01 00 08 00 00 00 |..xA............| 000000a0 00 00 00 00 00 00 00 00 ee 3d 28 00 00 00 00 00 |.........=(.....| 000000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000000c0  00 00 00 00 00                                    |.....|
000000c5
$ hexdump -C dev/shm/resolvconf/interface/eth0.inet
00000000 a4 81 00 00 d6 75 0d 00 2a 57 1e 43 1d 8d 1f 43 |.....u..*W.C...C| 00000010 c1 bc 78 41 00 00 00 00 00 00 01 00 c8 06 00 00 |..xA............| 00000020 00 00 00 00 00 00 00 00 11 3b 28 00 12 3b |.........;(..;|
0000002e

That really shouldn't be happening.

(ifstate should look something like this:
$ cat /dev/shm/network/ifstate
lo=lo
eth0=eth0
)


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Weird tmpfs behavior -- getting trashed, Eric Brown <=