Linux-LVM Archive mirror
 help / color / mirror / Atom feed
From: Peter Bartosch <peter@bartosch.net>
To: Reiserfs List <reiserfs-list@namesys.com>
Cc: Linux LVM List <linux-lvm@sistina.com>
Subject: [linux-lvm] Re: [reiserfs-list] Reiserfs fragments my MP3
Date: Sun, 10 Jun 2001 22:27:19 +0200	[thread overview]
Message-ID: <20010610222719.B21955@mind.bartosch.net> (raw)
In-Reply-To: <20010610222138.A21955@mind.bartosch.net>; from peter@bartosch.net on Sun, Jun 10, 2001 at 10:21:38PM +0200

Hi!


> hello,
> 
> 
> i just noticed that my new reiserfs on an LVM fragments my MP3
> 
> 
> mpg123 -t shows me:
> 
> mpg123: Can't rewind stream by 95 bits!
> Frame#    89 [ 8156], Time: 00:01.35 [03:34.02], [  171520] mpg123:
> Can't rewind stream by 337 bits!
> Frame#   122 [ 8123], Time: 00:02.66 [03:32.71], [   91904] mpg123:
> Can't rewind stream by 89 bits!
> Frame#   134 [ 8111], Time: 00:02.69 [03:32.68], [  142592] mpg123:
> Can't rewind stream by 410 bits!
> Frame#   142 [ 8103], Time: 00:02.71 [03:32.66], [  174848] mpg123:
> Can't rewind stream by 165 bits!
> Frame#   234 [ 8011], Time: 00:05.34 [03:30.03], [  135424] mpg123:
> Can't rewind stream by 56 bits!
> Frame#   251 [ 7994], Time: 00:05.35 [03:30.02], [  211456] mpg123:
> Can't rewind stream by 19 bits!
> Frame#   254 [ 7991], Time: 00:05.37 [03:30.00], [  222976] mpg123:
> Can't rewind stream by 2 bits!
> Frame#   262 [ 7983], Time: 00:05.39 [03:29.98], [  255232] mpg123:
> Can't rewind stream by 38 bits!
> Frame#   273 [ 7972], Time: 00:06.72 [03:28.65], [   71936] mpg123:
> Can't rewind stream by 66 bits!
> Frame#   274 [ 7971], Time: 00:06.74 [03:28.62], [   71936] mpg123:
> Can't rewind stream by 165 bits!
> Frame#   275 [ 7970], Time: 00:06.77 [03:28.60], [   71936] mpg123:
> Can't rewind stream by 15 bits!
> 
> 
> this file was ok before i copied it to this volume
> 
> 
> my kernel is 2.4.5 with the LVM parts of -AA2
> 
> hmm, i haven't this with an "normal" partition

i just tested it with a normal partition - that works -- so i think i
had to adress this to linux-lvm ...

> 
> :wq - until next mail B-), l8r
> 
> Peter
> -- 
>    :~~~~~~~~~~~~~~~~~~  peter@bartosch.net  ~~~~~~~~~~~~~~~~~~:
>    :          student of technical computer science           :
>    :     university of applied sciences krefeld (germany)     :
>     ~~~~~~~~~~~~~~~~~~~~~~ gpg: 40c9053e ~~~~~~~~~~~~~~~~~~~~~

:wq - until next mail B-), l8r

Peter
-- 
   :~~~~~~~~~~~~~~~~~~  peter@bartosch.net  ~~~~~~~~~~~~~~~~~~:
   :          student of technical computer science           :
   :     university of applied sciences krefeld (germany)     :
    ~~~~~~~~~~~~~~~~~~~~~~ gpg: 40c9053e ~~~~~~~~~~~~~~~~~~~~~

       reply	other threads:[~2001-06-10 20:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010610222138.A21955@mind.bartosch.net>
2001-06-10 20:27 ` Peter Bartosch [this message]
2001-06-11  4:44   ` [linux-lvm] Re: [reiserfs-list] Reiserfs fragments my MP3 Peter Bartosch
2001-06-11 13:49     ` Ragnar Kjørstad
2001-06-12 12:06       ` David Vidal Rodriguez
2020-11-27 16:17         ` Holger Grothe
2001-06-12 15:43           ` Werner John

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010610222719.B21955@mind.bartosch.net \
    --to=peter@bartosch.net \
    --cc=linux-lvm@sistina.com \
    --cc=reiserfs-list@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).