On Sun, Mar 27, 2016 at 03:25:40AM -, DD Park wrote:
> Hello, I need your help. This bug seemed to have been placed offline due to
> inactivity. It is still a problem as been working on moving things around
> to get a testing platform. I've been getting new hardware, and started
> another
Hello, I need your help. This bug seemed to have been placed offline due to
inactivity. It is still a problem as been working on moving things around
to get a testing platform. I've been getting new hardware, and started
another build process to get me to a point of testing. I'm plan on doing a
Hi. The problem still exists for me, I haven't been able to get equipment
yet, but the data is still sitting on a bunch of hard drives.
On Sun, Jan 17, 2016 at 8:18 PM, Launchpad Bug Tracker <
1345...@bugs.launchpad.net> wrote:
> [Expired for e2fsprogs (Ubuntu) because there has been no activity
[Expired for e2fsprogs (Ubuntu) because there has been no activity for
60 days.]
** Changed in: e2fsprogs (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
To jump in for Ted here; I'm pretty sure that "very large" is in the
millions range. Whatever the cause though, the best way for us to be
able to reproduce, diagnose, and fix it is with an image of the
filesystem, even if it is with the file names scrambled ( the names
don't really matter anyhow,
Hi. I checked into another server that is waiting to upgrade >16TB
pending this issue get resolved.
Can you provide more information as to the statement "very large
number of hard link". This other system has approx 150K hardlinks and
growing daily. I'm not sure if we are talking about millions or
the nature of the content is confidential so I wouldnt' be able to get you
an e2image of the file system. it has live data. I am guessing that it is
possibly the high number of files or the nature of the file system
corruption.
I know that the fsck was not clean, and it just keeps sucking up
You do realize that e2image doesn't contain any data blocks --- just
file system metadata blocks, right? And if you are concerned about the
directory names being too revealing, e2image has a -s option which will
scramble the directory file names. See the section "RAW IMAGE FILES" in
the e2image
I am not familiar with the tool, but I was concerned about the
file/directory names. I can look into the -s option
and might be doable. I am still without a working chassis that can handle
as many harddrives I have. I have
a new motherboard and card. I was able to find online other people having
There are plenty of people who *are* able to check file systems larger than
16TB. So talking about it in terms "that problem" doesn't make much sense.
FYI. There was about 15TB (back when I initially ran into the problem,
maybe about 11-14TB) of hardlinks.
The Hardlinks are used so that rsync can handle directory name changes and
not have to copy the whole directory over again. Thus each file would have
a hardlink. I estimate maybe 40K+ or 80K+
As of 1 month ago I was still having the problem. The chassis last month
has failed and i don't have another chassis that can handle that many
drives. I am on hold until I can get funding to get another chassis. I have
moved to 6TB drives for another setup, but I limited the partition to 16TB
I just tried a fresh install of 14.04.2 in a vm with a 20 tb virtual
disk and fsck seemed to work fine. It might be specific to your disk
contents. If you can reproduce this, please capture an image of the
filesystem metadata with e2image -r ( and bzip2 that ) and attach it and
I can try running
Are you still able to reproduce this?
** Package changed: util-linux (Ubuntu) => e2fsprogs (Ubuntu)
** Changed in: e2fsprogs (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
14 matches
Mail list logo
